| Replied (other) | psql security fail? | over 12 years ago |
| Started thread | pgsql: Get rid of more cases of the "must detoast before output functio | over 12 years ago |
| Started thread | pgsql: Prevent memory leaks from accumulating across printtup() calls. | over 12 years ago |
| Started thread | pgsql: Prevent memory leaks from accumulating across printtup() calls. | over 12 years ago |
| Started thread | pgsql: Prevent memory leaks from accumulating across printtup() calls. | over 12 years ago |
| Replied (other) | pgsql: Changed test case slightly so it doesn't have an unused typedef. | over 12 years ago |
| Replied (other) | Memory usage per postmaster process | over 12 years ago |
| Replied (other) | Creating Empty Index | over 12 years ago |
| Replied (other) | Problems with pg_stat_activity view | over 12 years ago |
| Replied (other) | BUG #8576: 'btree index keys must be ordered by attribute' | over 12 years ago |
| Started thread | pgsql: Retry after buffer locking failure during SPGiST index creation. | over 12 years ago |
| Started thread | pgsql: Retry after buffer locking failure during SPGiST index creation. | over 12 years ago |
| Started thread | pgsql: Retry after buffer locking failure during SPGiST index creation. | over 12 years ago |
| Replied (other) | SP-GiST bug and fix | over 12 years ago |
| Replied (other) | Memory usage per postmaster process | over 12 years ago |
| Replied (other)First patch | BUG #8573: int4range memory consumption | over 12 years ago |
| Replied (other) | Add accurate option to pgbench | over 12 years ago |
| Replied (other) | pg_dump with lots and lots of tables | over 12 years ago |
| Replied (other) | Record comparison compiler warning | over 12 years ago |
| Replied (other) | Feature request: optimizer improvement | over 12 years ago |
| Replied (other) | Why release index relation lock | over 12 years ago |
| Replied (other) | appendPQExpBufferVA vs appendStringInfoVA | over 12 years ago |
| Replied (other) | Problems with pg_stat_activity view | over 12 years ago |
| Replied (other) | BUG #8573: int4range memory consumption | over 12 years ago |
| Replied (other) | Feature request: optimizer improvement | over 12 years ago |
| Started thread | pgsql: Ensure all files created for a single BufFile have the same reso | over 12 years ago |
| Started thread | pgsql: Ensure all files created for a single BufFile have the same reso | over 12 years ago |
| Started thread | pgsql: Ensure all files created for a single BufFile have the same reso | over 12 years ago |
| Started thread | pgsql: Ensure all files created for a single BufFile have the same reso | over 12 years ago |
| Started thread | pgsql: Ensure all files created for a single BufFile have the same reso | over 12 years ago |
| Started thread | pgsql: Ensure all files created for a single BufFile have the same reso | over 12 years ago |
| Replied (other) | buffile.c resource owner breakage on segment extension | over 12 years ago |
| Replied (other) | BUG #8573: int4range memory consumption | over 12 years ago |
| Replied (other) | json datatype and table bloat? | over 12 years ago |
| Replied (other) | BUG #8572: Combination of SET TIME ZONEs and CAST gives wrong results | over 12 years ago |
| Started thread | pgsql: Remove CTimeZone/HasCTZSet, root and branch. | over 12 years ago |
| Started thread | pgsql: Remove internal uses of CTimeZone/HasCTZSet. | over 12 years ago |
| Started thread | pgsql: Fix some odd behaviors when using a SQL-style simple GMT offset | over 12 years ago |
| Started thread | pgsql: Fix some odd behaviors when using a SQL-style simple GMT offset | over 12 years ago |
| Started thread | pgsql: Fix some odd behaviors when using a SQL-style simple GMT offset | over 12 years ago |
| Started thread | pgsql: Fix some odd behaviors when using a SQL-style simple GMT offset | over 12 years ago |
| Started thread | pgsql: Fix some odd behaviors when using a SQL-style simple GMT offset | over 12 years ago |
| Started thread | pgsql: Fix some odd behaviors when using a SQL-style simple GMT offset | over 12 years ago |
| Replied (own) | API bug in DetermineTimeZoneOffset() | over 12 years ago |
| Replied (other) | Save Hash Indexes | over 12 years ago |
| Replied (other) | Save Hash Indexes | over 12 years ago |
| Replied (other) | Shave a few instructions from child-process startup sequence | over 12 years ago |
| Replied (own)First patch | API bug in DetermineTimeZoneOffset() | over 12 years ago |
| Replied (own) | API bug in DetermineTimeZoneOffset() | over 12 years ago |
| Replied (own) | API bug in DetermineTimeZoneOffset() | over 12 years ago |
| Replied (other) | Get more from indices. | over 12 years ago |
| Started thread | API bug in DetermineTimeZoneOffset() | over 12 years ago |
| Replied (other) | BUG #8571: Planner miss-estimates '<null_column> is not true' as not matching any rows | over 12 years ago |
| Replied (other) | Get more from indices. | over 12 years ago |
| Replied (own) | Something fishy happening on frogmouth | over 12 years ago |
| Replied (other) | problem with partitioned table and indexed json field | over 12 years ago |
| Replied (other) | permission denied | over 12 years ago |
| Replied (other) | array_agg() on a set larger than some arbitrary(?) limit causes runaway memory usage and eventually memory exhaustion | over 12 years ago |
| Replied (own) | Something fishy happening on frogmouth | over 12 years ago |
| Replied (other) | How can I build OSSP UUID support on Windows to avoid duplicate UUIDs? | over 12 years ago |
| Replied (own) | Something fishy happening on frogmouth | over 12 years ago |
| Replied (other) | How can I build OSSP UUID support on Windows to avoid duplicate UUIDs? | over 12 years ago |
| Replied (own) | Something fishy happening on frogmouth | over 12 years ago |
| Replied (other) | patch: add MAP_HUGETLB to mmap() where supported (WIP) | over 12 years ago |
| Replied (other) | patch: add MAP_HUGETLB to mmap() where supported (WIP) | over 12 years ago |
| Replied (other) | No reply-to in list messages. | over 12 years ago |
| Replied (own) | Something fishy happening on frogmouth | over 12 years ago |
| Replied (own) | Something fishy happening on frogmouth | over 12 years ago |
| Replied (other) | patch: add MAP_HUGETLB to mmap() where supported (WIP) | over 12 years ago |
| Replied (other) | How should row-security affects ON UPDATE RESTRICT / CASCADE ? | over 12 years ago |
| Replied (other) | BUG #8568: PLPGSQL Documentation For CASE Is incorrect | over 12 years ago |
| Replied (other) | json datatype and table bloat? | over 12 years ago |
| Replied (other) | json datatype and table bloat? | over 12 years ago |
| Started thread | pgsql: Fix old typo in comment. | over 12 years ago |
| Started thread | Something fishy happening on frogmouth | over 12 years ago |
| Replied (other) | Fast insertion indexes: why no developments | over 12 years ago |
| Replied (other) | surprising to_timestamp behavior | over 12 years ago |
| Replied (other) | Fast insertion indexes: why no developments | over 12 years ago |
| Replied (other) | Fast insertion indexes: why no developments | over 12 years ago |
| Replied (other) | How should row-security affects ON UPDATE RESTRICT / CASCADE ? | over 12 years ago |
| Replied (other) | INSERT/UPDATE statements sometimes choosing not to use PK index? | over 12 years ago |
| Replied (other) | Darwin: make check fails with "child process exited with exit code 134" | over 12 years ago |
| Replied (other) | Darwin: make check fails with "child process exited with exit code 134" | over 12 years ago |
| Replied (other) | Darwin: make check fails with "child process exited with exit code 134" | over 12 years ago |
| Replied (other) | What hook would you recommend for "one time, post authentication"? | over 12 years ago |
| Replied (other) | Darwin: make check fails with "child process exited with exit code 134" | over 12 years ago |
| Started thread | pgsql: Prevent using strncpy with src == dest in TupleDescInitEntry. | over 12 years ago |
| Started thread | pgsql: Prevent using strncpy with src == dest in TupleDescInitEntry. | over 12 years ago |
| Started thread | pgsql: Prevent using strncpy with src == dest in TupleDescInitEntry. | over 12 years ago |
| Started thread | pgsql: Prevent using strncpy with src == dest in TupleDescInitEntry. | over 12 years ago |
| Started thread | pgsql: Prevent using strncpy with src == dest in TupleDescInitEntry. | over 12 years ago |
| Started thread | pgsql: Prevent using strncpy with src == dest in TupleDescInitEntry. | over 12 years ago |
| Replied (other) | Re: better atomics | over 12 years ago |
| Replied (other) | Detection of nested function calls | over 12 years ago |
| Replied (other) | Re: better atomics | over 12 years ago |
| Replied (other) | Darwin: make check fails with "child process exited with exit code 134" | over 12 years ago |
| Replied (other) | Darwin: make check fails with "child process exited with exit code 134" | over 12 years ago |
| Replied (other) | Detection of nested function calls | over 12 years ago |
| Replied (other) | Darwin: make check fails with "child process exited with exit code 134" | over 12 years ago |
| Replied (other) | Darwin: make check fails with "child process exited with exit code 134" | over 12 years ago |
| Replied (other) | Detection of nested function calls | over 12 years ago |
| Replied (other) | Detection of nested function calls | over 12 years ago |
| Replied (other) | Darwin: make check fails with "child process exited with exit code 134" | over 12 years ago |
| Replied (other) | RULE regression test fragility? | over 12 years ago |
| Replied (other) | Darwin: make check fails with "child process exited with exit code 134" | over 12 years ago |
| Replied (other) | Darwin: make check fails with "child process exited with exit code 134" | over 12 years ago |
| Replied (other) | RULE regression test fragility? | over 12 years ago |
| Replied (other) | Detection of nested function calls | over 12 years ago |
| Replied (other) | Document update in alter_foreign_data_wrapper.sgml | over 12 years ago |
| Started thread | pgsql: Improve documentation about usage of FDW validator functions. | over 12 years ago |
| Started thread | pgsql: Improve documentation about usage of FDW validator functions. | over 12 years ago |
| Started thread | pgsql: Suppress duplicate-index-entry warning introduced by previous co | over 12 years ago |