| Replied (other) | AIX 7.1 compile and initdb error TRAP: FailedAssertion | almost 11 years ago |
| Started thread | pgsql: Tweak wording of syntax error messages about bad CONTINUE/EXIT s | almost 11 years ago |
| Replied (other) | PostgreSQL for VAX on NetBSD/OpenBSD | almost 11 years ago |
| Started thread | pgsql: Reduce number of bytes examined by convert_one_string_to_scalar( | almost 11 years ago |
| Replied (other) | Problem with pl/python procedure connecting to the internet | almost 11 years ago |
| Replied (own) | pgsql: Avoid use of float arithmetic in bipartite_match.c. | almost 11 years ago |
| Replied (other) | PostgreSQL for VAX on NetBSD/OpenBSD | almost 11 years ago |
| Replied (other) | PostgreSQL for VAX on NetBSD/OpenBSD | almost 11 years ago |
| Started thread | pgsql: Avoid use of float arithmetic in bipartite_match.c. | almost 11 years ago |
| Started thread | pgsql: Avoid use of float arithmetic in bipartite_match.c. | almost 11 years ago |
| Replied (other) | PostgreSQL for VAX on NetBSD/OpenBSD | almost 11 years ago |
| Replied (other) | PostgreSQL for VAX on NetBSD/OpenBSD | almost 11 years ago |
| Replied (other) | Error message with plpgsql CONTINUE | almost 11 years ago |
| Replied (other) | (full) Memory context dump considered harmful | almost 11 years ago |
| Replied (other) | PostgreSQL Developer Best Practices | almost 11 years ago |
| Replied (other) | PostgreSQL for VAX on NetBSD/OpenBSD | almost 11 years ago |
| Replied (other) | (full) Memory context dump considered harmful | almost 11 years ago |
| Replied (other) | Converting char to varchar automatically | almost 11 years ago |
| Replied (other) | Memory allocation in spi_printtup() | almost 11 years ago |
| Started thread | pgsql: Avoid O(N^2) behavior when enlarging SPI tuple table in spi_prin | almost 11 years ago |
| Started thread | pgsql: Avoid O(N^2) behavior when enlarging SPI tuple table in spi_prin | almost 11 years ago |
| Started thread | pgsql: Avoid O(N^2) behavior when enlarging SPI tuple table in spi_prin | almost 11 years ago |
| Started thread | pgsql: Avoid O(N^2) behavior when enlarging SPI tuple table in spi_prin | almost 11 years ago |
| Started thread | pgsql: Avoid O(N^2) behavior when enlarging SPI tuple table in spi_prin | almost 11 years ago |
| Started thread | pgsql: Avoid O(N^2) behavior when enlarging SPI tuple table in spi_prin | almost 11 years ago |
| Started thread | pgsql: Avoid O(N^2) behavior when enlarging SPI tuple table in spi_prin | almost 11 years ago |
| Replied (other) | Error message with plpgsql CONTINUE | almost 11 years ago |
| Started thread | pgsql: Detect mismatched CONTINUE and EXIT statements at plpgsql compil | almost 11 years ago |
| Replied (other) | ERROR: invalid input syntax for type date: IS IT A BUG here? | almost 11 years ago |
| Replied (other)First patch | (full) Memory context dump considered harmful | almost 11 years ago |
| Replied (other) | More WITH | almost 11 years ago |
| Replied (other) | More WITH | almost 11 years ago |
| Replied (other) | (full) Memory context dump considered harmful | almost 11 years ago |
| Replied (other) | Warnings around booleans | almost 11 years ago |
| Replied (other) | Warnings around booleans | almost 11 years ago |
| Replied (other) | A few cases of left shifting negative integers | almost 11 years ago |
| Replied (other) | A few cases of left shifting negative integers | almost 11 years ago |
| Replied (other) | Make HeapTupleSatisfiesMVCC more concurrent | almost 11 years ago |
| Replied (other) | BUG #13579: Server crashes after executing plpythonu function | almost 11 years ago |
| Started thread | pgsql: Fix plpython crash when returning string representation of a REC | almost 11 years ago |
| Started thread | pgsql: Allow record_in() and record_recv() to work for transient record | almost 11 years ago |
| Started thread | pgsql: Allow record_in() and record_recv() to work for transient record | almost 11 years ago |
| Started thread | pgsql: Fix plpython crash when returning string representation of a REC | almost 11 years ago |
| Started thread | pgsql: Fix plpython crash when returning string representation of a REC | almost 11 years ago |
| Started thread | pgsql: Fix plpython crash when returning string representation of a REC | almost 11 years ago |
| Started thread | pgsql: Allow record_in() and record_recv() to work for transient record | almost 11 years ago |
| Started thread | pgsql: Allow record_in() and record_recv() to work for transient record | almost 11 years ago |
| Started thread | pgsql: Fix plpython crash when returning string representation of a REC | almost 11 years ago |
| Started thread | pgsql: Fix plpython crash when returning string representation of a REC | almost 11 years ago |
| Started thread | pgsql: Allow record_in() and record_recv() to work for transient record | almost 11 years ago |
| Started thread | pgsql: Allow record_in() and record_recv() to work for transient record | almost 11 years ago |
| Replied (other) | 9.5 release notes | almost 11 years ago |
| Replied (other) | BUG #13583: Documentation "5.8.2. The Public Schema" misleading | almost 11 years ago |
| Started thread | pgsql: Remove xpath namespace-handling change from 9.5 release notes. | almost 11 years ago |
| Replied (other) | (full) Memory context dump considered harmful | almost 11 years ago |
| Replied (other) | PostgreSQL for VAX on NetBSD/OpenBSD | almost 11 years ago |
| Replied (other) | Extension upgrade and GUCs | almost 11 years ago |
| Replied (other) | Supporting fallback RADIUS server(s) | almost 11 years ago |
| Replied (other) | BUG #13580: Fix namespace handling in xpath function, current functions collision | almost 11 years ago |
| Replied (other) | Using quicksort for every external sort run | almost 11 years ago |
| Replied (other) | BUG #13581: pg_dump omits extension versions | almost 11 years ago |
| Replied (other) | Supporting fallback RADIUS server(s) | almost 11 years ago |
| Replied (other) | proposal: function parse_ident | almost 11 years ago |
| Replied (own)First patch | Badly broken logic in plpython composite-type handling | almost 11 years ago |
| Replied (other) | Mention column name in error messages | almost 11 years ago |
| Replied (other) | Our trial to TPC-DS but optimizer made unreasonable plan | almost 11 years ago |
| Replied (other) | Memory leak with PL/Python trigger | almost 11 years ago |
| Replied (other) | proposal: function parse_ident | almost 11 years ago |
| Replied (other) | Proposal: Implement failover on libpq connect level. | almost 11 years ago |
| Started thread | Badly broken logic in plpython composite-type handling | almost 11 years ago |
| Replied (other) | BUG #13579: Server crashes after executing plpythonu function | almost 11 years ago |
| Replied (other) | Make HeapTupleSatisfiesMVCC more concurrent | almost 11 years ago |
| Replied (other) | Bug? ExecChooseHashTableSize() got assertion failed with crazy number of rows | almost 11 years ago |
| Replied (other) | Make HeapTupleSatisfiesMVCC more concurrent | almost 11 years ago |
| Replied (other) | Bug? ExecChooseHashTableSize() got assertion failed with crazy number of rows | almost 11 years ago |
| Replied (other) | DBT-3 with SF=20 got failed | almost 11 years ago |
| Replied (other) | Proposal: Implement failover on libpq connect level. | almost 11 years ago |
| Replied (other) | More WITH | almost 11 years ago |
| Replied (other) | Bug? ExecChooseHashTableSize() got assertion failed with crazy number of rows | almost 11 years ago |
| Replied (other)Follow-up patch | Make HeapTupleSatisfiesMVCC more concurrent | almost 11 years ago |
| Replied (other) | Make HeapTupleSatisfiesMVCC more concurrent | almost 11 years ago |
| Started thread | pgsql: Fix a few bogus statement type names in plpgsql error messages. | almost 11 years ago |
| Started thread | pgsql: Fix a few bogus statement type names in plpgsql error messages. | almost 11 years ago |
| Started thread | pgsql: Fix a few bogus statement type names in plpgsql error messages. | almost 11 years ago |
| Started thread | pgsql: Fix a few bogus statement type names in plpgsql error messages. | almost 11 years ago |
| Started thread | pgsql: Fix a few bogus statement type names in plpgsql error messages. | almost 11 years ago |
| Started thread | pgsql: Fix a few bogus statement type names in plpgsql error messages. | almost 11 years ago |
| Started thread | pgsql: Fix a few bogus statement type names in plpgsql error messages. | almost 11 years ago |
| Replied (other) | Error message with plpgsql CONTINUE | almost 11 years ago |
| Replied (other) | BUG #13578: use cipher=NULL-SHA256 error when connect | almost 11 years ago |
| Replied (other) | How to get cursor query | almost 11 years ago |
| Replied (other) | allowing wal_level change at run time | almost 11 years ago |
| Replied (other) | How to get cursor query | almost 11 years ago |
| Started thread | pgsql: Fix performance bug from conflict between two previous improveme | almost 11 years ago |
| Replied (other) | jsonb array-style subscripting | almost 11 years ago |
| Replied (other) | Error message with plpgsql CONTINUE | almost 11 years ago |
| Replied (other) | jsonb array-style subscripting | almost 11 years ago |
| Replied (other) | More WITH | almost 11 years ago |
| Replied (other) | Memory allocation in spi_printtup() | almost 11 years ago |
| Replied (other) | Error message with plpgsql CONTINUE | almost 11 years ago |
| Replied (other) | stack depth | almost 11 years ago |