| Replied (other) | Proposal for Allow postgresql.conf values to be changed via SQL | over 13 years ago |
| Replied (other) | What are the advantages of not being able to access multiple databases with one connection? | over 13 years ago |
| Replied (own) | Is there a way to test for UNASSIGNED in pl/pgsql | over 13 years ago |
| Started thread | Is there a way to test for UNASSIGNED in pl/pgsql | over 13 years ago |
| Replied (own) | Should "select 'nan'::float = 'nan'::float;" return false as per IEEE 754 | over 13 years ago |
| Replied (own) | Should "select 'nan'::float = 'nan'::float;" return false as per IEEE 754 | over 13 years ago |
| Started thread | Should "select 'nan'::float = 'nan'::float;" return false as per IEEE 754 | over 13 years ago |
| Replied (own) | [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility | over 13 years ago |
| Replied (own) | [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility | over 13 years ago |
| Replied (own) | [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility | over 13 years ago |
| Replied (own) | [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility | over 13 years ago |
| Replied (own) | [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility | over 13 years ago |
| Replied (own) | [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility | over 13 years ago |
| Replied (own) | [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility | over 13 years ago |
| Replied (other) | Deprecating RULES | over 13 years ago |
| Replied (own) | [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility | over 13 years ago |
| Replied (own) | [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility | over 13 years ago |
| Replied (own) | [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility | over 13 years ago |
| Started thread | [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility | over 13 years ago |
| Replied (other) | [RFC][PATCH] wal decoding, attempt #2 | over 13 years ago |
| Replied (other) | [RFC][PATCH] wal decoding, attempt #2 | over 13 years ago |
| Replied (other) | [RFC][PATCH] wal decoding, attempt #2 | over 13 years ago |
| Replied (other) | [RFC][PATCH] wal decoding, attempt #2 | over 13 years ago |
| Replied (other) | Deprecating RULES | over 13 years ago |
| Replied (other) | Truncate if exists | over 13 years ago |
| Replied (other) | Truncate if exists | over 13 years ago |
| Replied (other) | Deprecating RULES | over 13 years ago |
| Replied (other) | Deprecating RULES | over 13 years ago |
| Replied (other) | Deprecating RULES | over 13 years ago |
| Replied (other) | Deprecating RULES | over 13 years ago |
| Replied (other) | [RFC][PATCH] wal decoding, attempt #2 | over 13 years ago |
| Replied (other) | [RFC][PATCH] wal decoding, attempt #2 | over 13 years ago |
| Replied (own) | Is there a good reason why PL languages do not support cstring type arguments and return values ? | over 13 years ago |
| Replied (own) | Is there a good reason why PL languages do not support cstring type arguments and return values ? | over 13 years ago |
| Replied (own) | Is there a good reason why PL languages do not support cstring type arguments and return values ? | over 13 years ago |
| Started thread | Is there a good reason why PL languages do not support cstring type arguments and return values ? | over 13 years ago |
| Replied (other) | data to json enhancements | over 13 years ago |