Merge branch 'main' into nw_ignition

Author: nwoolmer

.gitignore

@@ -15,6 +15,7 @@ plugins/*/compiled
 .docusaurus
 .netlify
 .cache-loader
+static/llms.txt
 
 # Misc
 .DS_Store

documentation/ingestion-overview.md

@@ -48,7 +48,8 @@ trades,symbol=BTC-USD,side=sell price=39269.98,amount=0.001 1646762637710419000\
 trades,symbol=ETH-USD,side=buy price=2615.4,amount=0.002 1646762637764098000\n
 ```
 
-Once inside of QuestDB, it's yours to manipulate and query via extended SQL.
+Once inside of QuestDB, it's yours to manipulate and query via extended SQL. Please note that table and column names
+must follow the QuestDB [naming rules](/docs/reference/sql/create-table/#table-name).
 
 ## Message brokers and queues
 

documentation/partials/pgwire/_connection_issues.partial.mdx

@@ -0,0 +1,6 @@
+### Connection issues
+
+1. Verify QuestDB is running and listening on port **8812**.
+2. Check credentials and network access.
+3. Try a minimal query: `SELECT 1`.
+4. Inspect QuestDB server logs for connection or auth errors.

documentation/partials/pgwire/_highly_available_reads.partial.mdx

@@ -0,0 +1,11 @@
+## Highly-Available Reads with QuestDB Enterprise
+
+QuestDB Enterprise supports running [multiple replicas](https://questdb.com/docs/operations/replication/) to serve queries.
+Client applications can specify **multiple hosts** in the connection string. This ensures that initial connections
+succeed even if a node is down. If the connected node fails later, the application should catch the error, reconnect to
+another host, and retry the read.
+
+See our blog post for background and the companion repository for a minimal example:
+
+- Blog: [Highly-available reads with QuestDB](https://questdb.com/blog/highly-available-reads-with-questdb/)
+- Example: [questdb/questdb-ha-reads](https://github.com/questdb/questdb-ha-reads)

documentation/partials/pgwire/_known_limitations.partial.mdx

@@ -0,0 +1,5 @@
+## PGWire Known Limitations with QuestDB
+
+- Some PostgreSQL-specific features (complex transaction semantics, exotic data types, certain metadata calls) may not be fully supported.
+- Cursors/scrollable result sets and some ORM expectations may behave differently than in PostgreSQL.
+- Prefer **querying** via PGWire and **ingestion** via ILP for best throughput.

documentation/partials/pgwire/_query_errors.partial.mdx

@@ -0,0 +1,8 @@
+### Query Errors
+
+For query-related errors:
+
+1. Verify that the table you're querying exists
+2. Check the syntax of your SQL query
+3. Ensure that you're using the correct data types for parameters
+4. Look for any unsupported PostgreSQL features that might be causing issues

documentation/partials/pgwire/_timestamp_confusion.partial.mdx

@@ -0,0 +1,3 @@
+### Timestamp confusion
+
+- Remember: **QuestDB stores and encodes timestamps always as UTC**.