---
title: "Ann Baum (@anngbaum) | Hashnode"
description: "Ann Baum (@anngbaum) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@anngbaum"
---

@anngbaum

# Ann Baum

@anngbaum · Joined August 2024

## Comments

[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: 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.](https://hashnode.com/posts/rate-limiting-supabase-requests-with-postgresql-and-pgheaderkit/64f717aafee4891c8d66ce22/comment/67b7453cf4fec39b69d5b17b)

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

[This has been a huge help as I ran into the exact same series of issues – thank you! Since you use chrome.storage, I would just flag this concept of a storage adapter was very helpful for managing that under the hood: https://stackoverflow.com/questions/76572760/auth-in-chrome-extension-with-supabase/77161107#77161107](https://hashnode.com/posts/supabase-login-with-oauth-in-chrome-extensions/6580899f17c0d4536d7c89cb/comment/670d2f8f3f7e4aec9ff7603f)

Comment · Article · Oct 14, 2024 · [Supabase login with OAuth in Chrome extensions](https://hashnode.com/posts/supabase-login-with-oauth-in-chrome-extensions/6580899f17c0d4536d7c89cb)

[This is great – we just implemented rate limiting pretty much exactly as described here. Only small gotcha was the check\_rate\_limit() function – we forgot that we use HEAD requests to validate username availability during signup, important to exclude those in addition to GET!](https://hashnode.com/posts/rate-limiting-supabase-requests-with-postgresql-and-pgheaderkit/64f717aafee4891c8d66ce22/comment/66c743aa1b6225a7d840afed)

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