PostgreSQL database recommended specs
Credentials for PostgreSQL
Neynar’s role MUST have read and write on either the public schema or a dedicated schema for us. Replace “schema_name” and “username” to match your choice:
GRANT CREATE ON SCHEMA schema_name TO username;
GRANT USAGE ON SCHEMA schema_name TO username;
GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA schema_name TO username;
GRANT ALL PRIVILEGES ON ALL SEQUENCES IN SCHEMA schema_name TO username;
GRANT ALL PRIVILEGES ON ALL FUNCTIONS IN SCHEMA schema_name TO username;
ALTER DEFAULT PRIVILEGES IN SCHEMA schema_name
GRANT ALL PRIVILEGES ON TABLES TO username;
ALTER DEFAULT PRIVILEGES IN SCHEMA schema_name
GRANT ALL PRIVILEGES ON SEQUENCES TO username;
ALTER DEFAULT PRIVILEGES IN SCHEMA schema_name
GRANT ALL PRIVILEGES ON FUNCTIONS TO username;
Your database SHOULD be in AWS us-east-1 or equivalent for the lowest indexing lag. If not, additional data transfer charges will be needed.
The database SHOULD require SSL on connections.
The database MAY be in a private VPC, but the database MUST be “publicly accessible”.
The database SHOULD limit access by IP address. We will give you our static IP during setup.
Be VERY CAREFUL with database triggers. They can break things in very surprising ways. This article covers some of the pain we’ve seen.
99.9% availability uptime on the database