{"success":true,"data":{"query":"Postgres Mastery","limit":10,"count":6,"sources":["web_1779060041.hat","postgres_mastery.tah","web_1779060040.hat"],"synced":[],"results":[{"source":"web_1779060041.hat","text":"Supabase Documentation Learn how to get up and running with Supabase through tutorials, APIs and platform resources. Getting Started Set up and connect a database in just a few minutes. Start with Supabase AI prompts Products Database Supabase provides a full Postgres database for every project with Realtime functionality, database backups, extensions, and more. Auth Add and manage email and password, passwordless, OAuth, and mobile logins to your project through a suite of identity providers and APIs. Storage Store, organize, transform, and serve large files—fully integrated with your Postgres database with Row Level Security access policies. Realtime Listen to database changes, store and sync user states across clients, broadcast data to clients subscribed to a channel, and more. Edge Functions Globally distributed, server-side functions to execute your code closest to your users for the lowest latency. Modules AI & Vectors Cron Queues Data REST API GraphQL API Client Libraries JavaScript Flutter Python C# Swift Kotlin Migrate to Supabase Bring your existing data, auth and storage to Supabase following our migration guides. Explore more resources about /guides/resources Explore more resources Amazon RDS Auth0 Firebase Auth Firebase Storage Firestore Data Heroku MSSQL MySQL Neon Postgres Render Vercel Postgres Additional resources AI tools Develop with Supabase AI-first using plugins, MCP, and skills. Platform guides Learn more about the tools and services powering Supabase. Supabase CLI Use the CLI to develop, manage and deploy your projects. Management API Manage your Supabase projects and organizations. Integrations Explore a variety of integrations from Supabase partners. Supabase UI A collection of pre-built Supabase components to speed up your project. Troubleshooting Our troubleshooting guide for solutions to common Supabase issues. Self-Hosting Get started with self-hosting Supabase. More on Self-Hosting about /guides/self-hosting More on Self-Hosting Auth Realtime Storage Analytics","score":27.12400931168676,"links":[]},{"source":"web_1779060041.hat","text":"Getting Started Use Supabase with React Learn how to create a Supabase project, add some sample data to your database, and query the data from a React app. 1 Create a Supabase project Go to database.new and create a new Supabase project. Alternatively, you can create a project using the Management API: 1 # First, get your access token from https://supabase.com/dashboard/account/tokens 2 export SUPABASE_ACCESS_TOKEN = \" your-access-token \" 3 4 # List your organizations to get the organization ID 5 curl -H \" Authorization: Bearer $SUPABASE_ACCESS_TOKEN \" \\ 6 https://api.supabase.com/v1/organizations 7 8 # Create a new project (replace <org-id> with your organization ID) 9 curl -X POST https://api.supabase.com/v1/projects \\ 10 -H \" Authorization: Bearer $SUPABASE_ACCESS_TOKEN \" \\ 11 -H \" Content-Type: application/json \" \\ 12 -d ' { 13 \"organization_id\": \"<org-id>\", 14 \"name\": \"My Project\", 15 \"region\": \"us-east-1\", 16 \"db_pass\": \"<your-secure-password>\" 17 } ' When your project is up and running, go to the Table Editor section of the Dashboard, create a new table and insert some data. Then in the Integrations > Data API section of the Dashboard, expose the specific tables or functions you want to access. To automatically grant access for new tables and functions in public , enable Default privileges for new entities . Alternatively, you can run the following snippet in your project's SQL Editor . This creates an instruments table with some sample data, sets a secure baseline by setting only the privileges each Postgres role needs, and adds Row Level Security (RLS) for enhanced security for database data by default. 1 -- Create the table 2 create table instruments ( 3 id bigint primary key generated always as identity , 4 name text not null 5 ); 6 7 -- Insert sample data into the table 8 insert into instruments ( name ) 9 values 10 ( ' violin ' ), 11 ( ' viola ' ), 12 ( ' cello ' ); 13 14 -- Grant the privileges the role needs, which is read access 15 grant select on public . instruments to anon; 16 17 -- Enable row level security for the table 18 alter table instruments enable row level security ; Create an RLS policy to make the data in your table publicly readable: 1 -- Create a policy to allow the anon role to read from the instruments table 2 create policy \" public can read instruments \" 3 on public . instruments 4 for select to anon 5 using (true); 2 Create a React app Create a React app using a Vite template. Explore drop-in UI components for your Supabase app. UI components built on shadcn/ui that connect to Supabase via a single command. Explore Components Terminal 1 npm create vite@latest my-app -- --template react 3 Install the Supabase client library The fastest way to get started is to use the supabase-js client library which provides a convenient interface for working with Supabase from a React app. Navigate to the React app and install supabase-js . Terminal 1 cd my-app && npm install @supabase/supabase-js 4 Declare Supabase Environment Variables Create a .env.local file and populate with your Supabase connection variables: Project URL No project found Publishable key No project found .env.local 1 VITE_SUPABASE_URL=<SUBSTITUTE_SUPABASE_URL> 2 VITE_SUPABASE_PUBLISHABLE_KEY=<SUBSTITUTE_SUPABASE_PUBLISHABLE_KEY> Get API details # Now that you've created some database tables, you are ready to insert data using the auto-generated API. To do this, you need to get the Project URL and key from the project Connect dialog . Read the API keys docs for a full explanation of all key types and their uses. Changes to API keys Supabase is changing the way keys work to improve project security and developer experience. You can read the full announcement on GitHub . The older anon and service_role keys will work until the end of 2026 but we strongly encourage switching to and using the new publishable ( sb_publishable_xxx ) and secret ( sb_secret_xxx ) keys now. In most cases, you can get keys from the Project's Connect dialog , but if you want a specific key, you can find them in the Settings > API Keys section of the Dashboard. For legacy keys , copy the anon key for client-side operations and the service_role key for server-side operations from the Legacy API Keys tab. For new keys , open the API Keys tab, if you don't have a publishable key already, click Create new API Keys , and copy the value from the Publishable key section. 5 Query data from the app Replace the contents of App.jsx to add a getInstruments function to fetch the data and display the query result to the page using a Supabase client. src/App.jsx 1 import { useEffect , useState } from \" react \" ; 2 import { createClient } from \" @supabase/supabase-js \" ; 3 4 const supabase = createClient ( import . meta . env . VITE_SUPABASE_URL , import . meta . env . VITE_SUPABASE_PUBLISHABLE_KEY ) ; 5 6 function App () { 7 const [ instruments , setInstruments ] = useState ( [] ) ; 8 9 useEffect ( () => { 10 getInstruments () ; 11 }, [] ) ; 12 13 async function getInstruments () { 14 const { data , error } = await supabase . from ( \" instruments \" ) . select () ; 15 16 if ( error ) { 17 console . error ( error ) ; 18 return ; 19 } 20 21 setInstruments ( data ) ; 22 } 23 24 return ( 25 < ul > 26 { instruments . map ( ( instrument ) => ( 27 < li key = { instrument . name }>{ instrument . name }</ li > 28 )) } 29 </ ul > 30 ) ; 31 } 32 33 export default App ; 6 Start the app Run the development server, go to http://localhost:5173 in a browser and you should see the list of instruments. Terminal 1 npm run dev Next steps # Set up Auth for your app Insert more data into your database Upload and serve static files using Storage Is this helpful? No Yes AI Tools Copy as Markdown Ask ChatGPT Ask Claude","score":27.12400931168676,"links":[]},{"source":"web_1779060041.hat","text":"Getting Started Use Supabase with Next.js Learn how to create a Supabase project, add some sample data, and query from a Next.js app. 1 Create a Supabase project Go to database.new and create a new Supabase project. Alternatively, you can create a project using the Management API: 1 # First, get your access token from https://supabase.com/dashboard/account/tokens 2 export SUPABASE_ACCESS_TOKEN = \" your-access-token \" 3 4 # List your organizations to get the organization ID 5 curl -H \" Authorization: Bearer $SUPABASE_ACCESS_TOKEN \" \\ 6 https://api.supabase.com/v1/organizations 7 8 # Create a new project (replace <org-id> with your organization ID) 9 curl -X POST https://api.supabase.com/v1/projects \\ 10 -H \" Authorization: Bearer $SUPABASE_ACCESS_TOKEN \" \\ 11 -H \" Content-Type: application/json \" \\ 12 -d ' { 13 \"organization_id\": \"<org-id>\", 14 \"name\": \"My Project\", 15 \"region\": \"us-east-1\", 16 \"db_pass\": \"<your-secure-password>\" 17 } ' When your project is up and running, go to the Table Editor section of the Dashboard, create a new table and insert some data. Then in the Integrations > Data API section of the Dashboard, expose the specific tables or functions you want to access. To automatically grant access for new tables and functions in public , enable Default privileges for new entities . Alternatively, you can run the following snippet in your project's SQL Editor . This creates an instruments table with some sample data, sets a secure baseline by setting only the privileges each Postgres role needs, and adds Row Level Security (RLS) for enhanced security for database data by default. 1 -- Create the table 2 create table instruments ( 3 id bigint primary key generated always as identity , 4 name text not null 5 ); 6 7 -- Insert sample data into the table 8 insert into instruments ( name ) 9 values 10 ( ' violin ' ), 11 ( ' viola ' ), 12 ( ' cello ' ); 13 14 -- Grant the privileges the role needs, which is read access 15 grant select on public . instruments to anon; 16 17 -- Enable row level security for the table 18 alter table instruments enable row level security ; Create an RLS policy to make the data in your table publicly readable: 1 -- Create a policy to allow the anon role to read from the instruments table 2 create policy \" public can read instruments \" 3 on public . instruments 4 for select to anon 5 using (true); 2 Create a Next.js app Use the create-next-app command and the with-supabase template, to create a Next.js app pre-configured with: Cookie-based Auth TypeScript Tailwind CSS Explore drop-in UI components for your Supabase app. UI components built on shadcn/ui that connect to Supabase via a single command. Explore Components 1 npx create-next-app -e with-supabase 3 Declare Supabase Environment Variables Rename .env.example to .env.local and populate with your Supabase connection variables: Project URL No project found Publishable key No project found .env.local 1 NEXT_PUBLIC_SUPABASE_URL=<SUBSTITUTE_SUPABASE_URL> 2 NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY=<SUBSTITUTE_SUPABASE_PUBLISHABLE_KEY> Get API details # Now that you've created some database tables, you are ready to insert data using the auto-generated API. To do this, you need to get the Project URL and key from the project Connect dialog . Read the API keys docs for a full explanation of all key types and their uses. Changes to API keys Supabase is changing the way keys work to improve project security and developer experience. You can read the full announcement on GitHub . The older anon and service_role keys will work until the end of 2026 but we strongly encourage switching to and using the new publishable ( sb_publishable_xxx ) and secret ( sb_secret_xxx ) keys now. In most cases, you can get keys from the Project's Connect dialog , but if you want a specific key, you can find them in the Settings > API Keys section of the Dashboard. For legacy keys , copy the anon key for client-side operations and the service_role key for server-side operations from the Legacy API Keys tab. For new keys , open the API Keys tab, if you don't have a publishable key already, click Create new API Keys , and copy the value from the Publishable key section. 4 Query Supabase data from Next.js Create a new file at app/instruments/page.tsx and populate with the following. This selects all the rows from the instruments table in Supabase and render them on the page. app/instruments/page.tsx 1 import { createClient } from \" @/lib/supabase/server \" ; 2 import { Suspense } from \" react \" ; 3 4 async function InstrumentsData () { 5 const supabase = await createClient () ; 6 const { data : instruments } = await supabase . from ( \" instruments \" ) . select () ; 7 8 return < pre >{ JSON.stringify( instruments , null , 2 ) } </ pre > ; 9 } 10 11 export default function Instruments () { 12 return ( 13 < Suspense fallback = { <div>Loading instruments ...</ div > } > 14 < InstrumentsData /> 15 </ Suspense > 16 ) ; 17 } 5 Start the app Run the development server, go to http://localhost:3000/instruments in a browser and you should see the list of instruments. 1 npm run dev Next steps # Set up Auth for your app Insert more data into your database Upload and serve static files using Storage Is this helpful? No Yes AI Tools Copy as Markdown Ask ChatGPT Ask Claude","score":27.12400931168676,"links":[]},{"source":"postgres_mastery.tah","text":"PostgreSQL Performance: Use EXPLAIN (ANALYZE, BUFFERS) for query profiling. In serverless (Next.js), always use Supavisor (Transaction mode) to prevent connection exhaustion. Indexing: Use Covering Indexes (INCLUDE) for Index-Only scans. Anti-Patterns: Avoid 'SELECT *' and 'COUNT(*)' on large tables; use caching for counts.","score":15,"links":[]},{"source":"postgres_mastery.tah","text":"Hybrid Postgres Pattern: Combining pg_vector semantic search with RLS for secure AI retrieval. Always enforce RLS on the embedding tables to ensure users only retrieve semantic matches they are authorized to see. Use Supabase 'rpc' calls to handle complex vector math inside Security Definer functions for performance.\n\n[SWARM_LINKS] a11b9110ba4b -> UNRESOLVED, 72fad7cb9706 -> UNRESOLVED","score":15,"links":[]},{"source":"web_1779060040.hat","text":"PostgreSQL 18.4 Documentation Next PostgreSQL 18.4 Documentation The PostgreSQL Global Development Group Copyright © 1996–2026 The PostgreSQL Global Development Group Legal Notice Table of Contents Preface 1. What Is PostgreSQL ? 2. A Brief History of PostgreSQL 3. Conventions 4. Further Information 5. Bug Reporting Guidelines I. Tutorial 1. Getting Started 2. The SQL Language 3. Advanced Features II. The SQL Language 4. SQL Syntax 5. Data Definition 6. Data Manipulation 7. Queries 8. Data Types 9. Functions and Operators 10. Type Conversion 11. Indexes 12. Full Text Search 13. Concurrency Control 14. Performance Tips 15. Parallel Query III. Server Administration 16. Installation from Binaries 17. Installation from Source Code 18. Server Setup and Operation 19. Server Configuration 20. Client Authentication 21. Database Roles 22. Managing Databases 23. Localization 24. Routine Database Maintenance Tasks 25. Backup and Restore 26. High Availability, Load Balancing, and Replication 27. Monitoring Database Activity 28. Reliability and the Write-Ahead Log 29. Logical Replication 30. Just-in-Time Compilation ( JIT ) 31. Regression Tests IV. Client Interfaces 32. libpq — C Library 33. Large Objects 34. ECPG — Embedded SQL in C 35. The Information Schema V. Server Programming 36. Extending SQL 37. Triggers 38. Event Triggers 39. The Rule System 40. Procedural Languages 41. PL/pgSQL — SQL Procedural Language 42. PL/Tcl — Tcl Procedural Language 43. PL/Perl — Perl Procedural Language 44. PL/Python — Python Procedural Language 45. Server Programming Interface 46. Background Worker Processes 47. Logical Decoding 48. Replication Progress Tracking 49. Archive Modules 50. OAuth Validator Modules VI. Reference I. SQL Commands II. PostgreSQL Client Applications III. PostgreSQL Server Applications VII. Internals 51. Overview of PostgreSQL Internals 52. System Catalogs 53. System Views 54. Frontend/Backend Protocol 55. PostgreSQL Coding Conventions 56. Native Language Support 57. Writing a Procedural Language Handler 58. Writing a Foreign Data Wrapper 59. Writing a Table Sampling Method 60. Writing a Custom Scan Provider 61. Genetic Query Optimizer 62. Table Access Method Interface Definition 63. Index Access Method Interface Definition 64. Write Ahead Logging for Extensions 65. Built-in Index Access Methods 66. Database Physical Storage 67. Transaction Processing 68. System Catalog Declarations and Initial Contents 69. How the Planner Uses Statistics 70. Backup Manifest Format VIII. Appendixes A. PostgreSQL Error Codes B. Date/Time Support C. SQL Key Words D. SQL Conformance E. Release Notes F. Additional Supplied Modules and Extensions G. Additional Supplied Programs H. External Projects I. The Source Code Repository J. Documentation K. PostgreSQL Limits L. Acronyms M. Glossary N. Color Support O. Obsolete or Renamed Features Bibliography Index Next Preface","score":14.574771391695638,"links":[]}]},"metadata":{},"timestamp":"2026-07-08T22:46:01.791Z"}