---
title: "Comment by Ann Baum on \"Rate Limiting Supabase Requests with PostgreSQL and pg_headerkit\" | Hashnode"
description: "One additional gotcha here that we just ran into – an unexpected side effect of: CREATE UNLOGGED TABLE request_log ( id BIGINT GENERATED BY DEFAULT AS IDENTITY,"
url: "https://hashnode.com/posts/rate-limiting-supabase-requests-with-postgresql-and-pgheaderkit/64f717aafee4891c8d66ce22/comment/67b7453cf4fec39b69d5b17b"
---

[Discussion](https://hashnode.com/posts/rate-limiting-supabase-requests-with-postgresql-and-pgheaderkit/64f717aafee4891c8d66ce22)

Comment [Rate Limiting Supabase Requests with PostgreSQL and pg\_headerkit](https://hashnode.com/posts/rate-limiting-supabase-requests-with-postgresql-and-pgheaderkit/64f717aafee4891c8d66ce22)

[Ann Baum](https://hashnode.com/@anngbaum)

[Feb 20, 2025](https://hashnode.com/posts/rate-limiting-supabase-requests-with-postgresql-and-pgheaderkit/64f717aafee4891c8d66ce22/comment/67b7453cf4fec39b69d5b17b)

One additional gotcha here that we just ran into – an unexpected side effect of:

CREATE UNLOGGED TABLE request\_log ( id BIGINT GENERATED BY DEFAULT AS IDENTITY, ip inet NOT NULL, timestamp timestamptz DEFAULT NOW() );

was that while the request\_log table was unlogged, the sequence created by id (request\_log\_id\_seq) was logged. this led to us running into a bug when we attempted to update our Postgres: [postgrespro.com/list/thread-id/2707900](https://postgrespro.com/list/thread-id/2707900)

we were able to resolve (courtesy of Supabase infra team identifying the issue + Claude identifying the fix!) by altering the table to use an unlogged sequence instead.
