Discussion for users on SQL related matters.
| Thread | Author | Time | 
|---|---|---|
| Function with OUT parameter and Return Query | Hector Menchaca | 04:23 | 
| Re: Function with OUT parameter and Return Query | Guillaume Lelarge | 08:06 | 
| Re: Function with OUT parameter and Return Query | Hector Menchaca | 18:10 | 
| Thread | Author | Time | 
|---|---|---|
| could not access status of transaction pg_multixact issue | jim_yates | 18:00 | 
| Re: could not access status of transaction pg_multixact issue | Adrian Klaver | 18:40 | 
| Re: could not access status of transaction pg_multixact issue | Alvaro Herrera | 18:55 | 
| Re: could not access status of transaction pg_multixact issue | jim_yates | 19:43 | 
| Re: could not access status of transaction pg_multixact issue | Alvaro Herrera | 20:54 | 
| Re: could not access status of transaction pg_multixact issue | jim_yates | 21:26 | 
| Thread | Author | Time | 
|---|---|---|
| Re: could not access status of transaction pg_multixact issue | jim_yates | 14:07 | 
| Re: could not access status of transaction pg_multixact issue | Adrian Klaver | 15:01 | 
| Re: could not access status of transaction pg_multixact issue | Alvaro Herrera | 15:12 | 
| Re: could not access status of transaction pg_multixact issue | jim_yates | 17:02 | 
| Re: could not access status of transaction pg_multixact issue | Alvaro Herrera | 18:00 | 
| Re: could not access status of transaction pg_multixact issue | jim_yates | 20:17 | 
| Re: could not access status of transaction pg_multixact issue | Alvaro Herrera | 20:36 | 
| Re: could not access status of transaction pg_multixact issue | jim_yates | 21:51 | 
| Thread | Author | Time | 
|---|---|---|
| Re: could not access status of transaction pg_multixact issue | jim_yates | 14:37 | 
| Re: could not access status of transaction pg_multixact issue | Alvaro Herrera | 16:26 | 
| Thread | Author | Time | 
|---|---|---|
| Any postgres API available to get errorcode for PQerrorMessage | Roopeshakumar Narayansa Shalgar (rshalgar) | 08:17 | 
| Re: [GENERAL] Any postgres API available to get errorcode for PQerrorMessage | Tom Lane | 16:36 | 
| Re: Any postgres API available to get errorcode for PQerrorMessage | Rob Sargent | 16:37 | 
| Re: [GENERAL] Any postgres API available to get errorcode for PQerrorMessage | Roopeshakumar Narayansa Shalgar (rshalgar) | 16:48 | 
| Re: Any postgres API available to get errorcode for PQerrorMessage | John R Pierce | 17:21 | 
| Thread | Author | Time | 
|---|---|---|
| Re: Any postgres API available to get errorcode for PQerrorMessage | Yogesh. Sharma | 03:10 | 
| Re: library path problems? (was: Completely unrelated) | John R Pierce | 03:21 | 
| Re: library path problems? | Adrian Klaver | 03:45 | 
| Re: Any postgres API available to get errorcode for PQerrorMessage | Roopeshakumar Narayansa Shalgar (rshalgar) | 07:09 | 
| Re: Any postgres API available to get errorcode for PQerrorMessage | Adrian Klaver | 20:09 | 
| Thread | Author | Time | 
|---|---|---|
| querying within json | Tim Dudgeon | 14:55 | 
| Re: querying within json | Giuseppe Broccolo | 15:22 | 
| [OFFTOPIC] unsubscribe list | Roberto Oliveira dos Santos | 15:28 | 
| Re: [OFFTOPIC] unsubscribe list | Adrian Klaver | 15:58 | 
| Re: querying within json | Tim Dudgeon | 16:24 | 
| Re: querying within json | David G Johnston | 16:48 | 
| return encoding results 📎 | Emi Lu | 17:37 | 
| Re: return encoding results | Andreas Kretschmer | 17:45 | 
| Re: querying within json | Tim Dudgeon | 19:22 | 
| Thread | Author | Time | 
|---|---|---|
| INT8 / float casting question | Filip RembiaĆkowski | 14:58 | 
| best strategy for searching large text fields | Campbell, Lance | 14:59 | 
| Re: INT8 / float casting question | [email protected] | 15:15 | 
| Re: best strategy for searching large text fields | Julien Cigar | 15:17 | 
| Re: INT8 / float casting question | Adrian Klaver | 15:29 | 
| Re: INT8 / float casting question | Adrian Klaver | 15:45 |