| Replied (other) | Wierd performance issue with 8.1cvs | about 21 years ago |
| Started thread | Old-style OR indexscan slated for destruction | about 21 years ago |
| Started thread | pgsql: Adjust nodeBitmapIndexscan.c to not keep the index open across | about 21 years ago |
| Started thread | pgsql: Actually, nodeBitmapIndexscan.c doesn't need to create a standard | about 21 years ago |
| Replied (other) | Re: UNICODE/UTF-8 on win32 | about 21 years ago |
| Replied (other) | Had a problem with pg_clog | about 21 years ago |
| Replied (other) | Constant WAL replay | about 21 years ago |
| Started thread | pgsql: Put back example of using Result node to execute an INSERT. | about 21 years ago |
| Replied (other) | Constant WAL replay | about 21 years ago |
| Replied (other) | Wierd performance issue with 8.1cvs | about 21 years ago |
| Replied (other) | Bad n_distinct estimation; hacks suggested? | about 21 years ago |
| Replied (other) | lots of puzzling log messages | about 21 years ago |
| Replied (other) | Had a problem with pg_clog | about 21 years ago |
| Replied (other) | BUG #1620: triggers breaks with alter table (at least with plpythonu) | about 21 years ago |
| Replied (other) | Transactions and "create or replace function" | about 21 years ago |
| Replied (other) | possible TODO: read-only tables, select from indexes only. | about 21 years ago |
| Replied (other) | BUG #1618: EXTRACTing EPOCH from TIME WITH TIME ZONE is broken | about 21 years ago |
| Replied (other) | BUG #1617: TIME WITH TIME ZONE comparison is partially broken | about 21 years ago |
| Started thread | pgsql: Repair two TIME WITH TIME ZONE bugs found by Dennis Vshivkov. | about 21 years ago |
| Started thread | pgsql: Repair two TIME WITH TIME ZONE bugs found by Dennis Vshivkov. | about 21 years ago |
| Started thread | pgsql: Repair two TIME WITH TIME ZONE bugs found by Dennis Vshivkov. | about 21 years ago |
| Started thread | pgsql: Repair two TIME WITH TIME ZONE bugs found by Dennis Vshivkov. | about 21 years ago |
| Started thread | pgsql: Repair two TIME WITH TIME ZONE bugs found by Dennis Vshivkov. | about 21 years ago |
| Replied (other) | possible TODO: read-only tables, select from indexes only. | about 21 years ago |
| Started thread | pgsql: Remove useless argtype_inherit() code, and make consequent | about 21 years ago |
| Started thread | pgsql: Remove explicit FreeExprContext calls during plan node shutdown. | about 21 years ago |
| Replied (other) | BUG #1583: Locale problem | about 21 years ago |
| Started thread | pgsql: Add comment about checkpoint panic behavior during shutdown, per | about 21 years ago |
| Replied (other) | BUG #1608: integer negative limit in plpgsql function arguments | about 21 years ago |
| Started thread | pgsql: Allow -2147483648 to be treated as an INT4 rather than INT8 | about 21 years ago |
| Replied (other) | empty array can crash backend using int_array_enum from contrib. | about 21 years ago |
| Started thread | pgsql: Treat a zero-D array as empty in int_enum(), per | about 21 years ago |
| Replied (other) | V2 protocol -> 8.1 server | about 21 years ago |
| Started thread | pgsql: Recent changes got the sense of the notnull bit backwards in the | about 21 years ago |
| Started thread | pgsql: Define the right-hand input of AT TIME ZONE as a full a_expr | about 21 years ago |
| Replied (other) | BUG #1618: EXTRACTing EPOCH from TIME WITH TIME ZONE is broken | about 21 years ago |
| Replied (other) | V2 protocol -> 8.1 server | about 21 years ago |
| Replied (other) | BUG #1618: EXTRACTing EPOCH from TIME WITH TIME ZONE is broken | about 21 years ago |
| Replied (other) | empty array can crash backend using int_array_enum from contrib. | about 21 years ago |
| Started thread | pgsql: int_aggregate's int_enum() doesn't work correctly with arrays | about 21 years ago |
| Started thread | pgsql: int_aggregate's int_enum() doesn't work correctly with arrays | about 21 years ago |
| Started thread | pgsql: int_aggregate's int_enum() doesn't work correctly with arrays | about 21 years ago |
| Started thread | pgsql: int_aggregate's int_enum() doesn't work correctly with arrays | about 21 years ago |
| Started thread | pgsql: Turns out that my recent elimination of the 'redundant' | about 21 years ago |
| Started thread | pgsql: Teach choose_bitmap_and() to actually be choosy --- that is, try | about 21 years ago |
| Started thread | pgsql: Fix bogus EXPLAIN display of rowcount estimates for BitmapAnd and | about 21 years ago |
| Replied (other) | Woo hoo ... a whole new set of compiler headaches!! :) | about 21 years ago |
| Replied (other) | pg_dump serial UNIQUE NOT NULL PRIMARY KEY | about 21 years ago |
| Replied (other) | libpq Unicode support? | about 21 years ago |
| Started thread | pgsql: First cut at planner support for bitmap index scans. | about 21 years ago |
| Replied (own) | Bitmap scans vs. the statistics views | about 21 years ago |
| Replied (own) | Bitmap scans vs. the statistics views | about 21 years ago |
| Replied (own) | Bitmap scans vs. the statistics views | about 21 years ago |
| Replied (other) | libpq Unicode support? | about 21 years ago |
| Replied (other) | libpq Unicode support? | about 21 years ago |
| Replied (other) | libpq Unicode support? | about 21 years ago |
| Replied (other) | Woo hoo ... a whole new set of compiler headaches!! :) | about 21 years ago |
| Replied (other) | libpq Unicode support? | about 21 years ago |
| Replied (other) | plperl function fails to "fire" Slony trigger | about 21 years ago |
| Started thread | Bitmap scans vs. the statistics views | about 21 years ago |
| Replied (other) | Woo hoo ... a whole new set of compiler headaches!! :) | about 21 years ago |
| Replied (other) | Table modifications with dependent views - best practices? | about 21 years ago |
| Replied (other) | Woo hoo ... a whole new set of compiler headaches!! :) | about 21 years ago |
| Replied (other) | ShmemAlloc: out of memory | about 21 years ago |
| Replied (other) | PQfmod and varchars | about 21 years ago |
| Replied (other) | Waiting for Disconnect | about 21 years ago |
| Replied (other) | debug levels in server | about 21 years ago |
| Started thread | pgsql: Rethink original decision to use AND/OR Expr nodes to represent | about 21 years ago |
| Replied (other) | Postgres: pg_hba.conf, md5, pg_shadow, encrypted passwords | about 21 years ago |
| Replied (other) | Postgres: pg_hba.conf, md5, pg_shadow, encrypted passwords | about 21 years ago |
| Replied (other) | BUG #1609: Bug in interval datatype for 64 Bit timestamps | about 21 years ago |
| Replied (own) | pgsql: Install some slightly realistic cost estimation for bitmap index | about 21 years ago |
| Replied (own) | pgsql: Install some slightly realistic cost estimation for bitmap index | about 21 years ago |
| Replied (own) | pgsql: Install some slightly realistic cost estimation for bitmap index | about 21 years ago |
| Replied (other) | BUG #1609: Bug in interval datatype for 64 Bit timestamps | about 21 years ago |
| Replied (other) | Proposal for background vacuum full/cluster | about 21 years ago |
| Replied (other) | Postgres: pg_hba.conf, md5, pg_shadow, encrypted passwords | about 21 years ago |
| Replied (other) | Postgres: pg_hba.conf, md5, pg_shadow, encrypted passwords | about 21 years ago |
| Replied (own) | pgsql: Install some slightly realistic cost estimation for bitmap index | about 21 years ago |
| Replied (other) | WAL/PITR additional items | about 21 years ago |
| Started thread | pgsql: Install some slightly realistic cost estimation for bitmap index | about 21 years ago |
| Replied (other) | WAL/PITR additional items | about 21 years ago |
| Replied (other) | Proposal for background vacuum full/cluster | about 21 years ago |
| Replied (other) | WAL/PITR additional items | about 21 years ago |
| Replied (other) | Problem with PITR recovery | about 21 years ago |
| Started thread | pgsql: Make pg_ctl status do a kill() test to verify that the PID found | about 21 years ago |
| Started thread | pgsql: Make pg_ctl status do a kill() test to verify that the PID found | about 21 years ago |
| Started thread | pgsql: Add note clarifying that indexes that support ordered scans had | about 21 years ago |
| Replied (other) | Postgres: pg_hba.conf, md5, pg_shadow, encrypted passwords | about 21 years ago |
| Replied (other) | Problem with PITR recovery | about 21 years ago |
| Replied (other) | Postgres: pg_hba.conf, md5, pg_shadow, encrypted passwords | about 21 years ago |
| Started thread | pgsql: Don't try to run clauseless index scans on index types that don't | about 21 years ago |
| Started thread | pgsql: Don't try to run clauseless index scans on index types that don't | about 21 years ago |
| Started thread | pgsql: Don't try to run clauseless index scans on index types that don't | about 21 years ago |
| Started thread | pgsql: Don't try to run clauseless index scans on index types that don't | about 21 years ago |
| Started thread | pgsql: Don't try to run clauseless index scans on index types that don't | about 21 years ago |
| Replied (other) | Postgres: pg_hba.conf, md5, pg_shadow, encrypted passwords | about 21 years ago |
| Replied (other) | BUG #1608: integer negative limit in plpgsql function arguments | about 21 years ago |
| Replied (other) | Problem with PITR recovery | about 21 years ago |
| Replied (other) | Problem with PITR recovery | about 21 years ago |
| Replied (other) | BUG #1609: Bug in interval datatype for 64 Bit timestamps | about 21 years ago |
| Started thread | pgsql: Fix mis-display of negative fractional seconds in interval values | about 21 years ago |
| Started thread | pgsql: Fix mis-display of negative fractional seconds in interval values | about 21 years ago |
| Started thread | pgsql: Fix mis-display of negative fractional seconds in interval values | about 21 years ago |
| Started thread | pgsql: Fix mis-display of negative fractional seconds in interval values | about 21 years ago |
| Replied (other) | BUG #1609: Bug in interval datatype for 64 Bit timestamps | about 21 years ago |
| Replied (other) | BUG #1609: Bug in interval datatype for 64 Bit timestamps | about 21 years ago |
| Started thread | pgsql: Minor performance improvement: avoid unnecessary | about 21 years ago |
| Replied (other) | lots of puzzling log messages | about 21 years ago |
| Replied (other) | BUG #1608: integer negative limit in plpgsql function arguments | about 21 years ago |
| Replied (other) | Foreign keys on array elements | about 21 years ago |
| Replied (other) | HAVING <alias> ... | about 21 years ago |
| Replied (other) | postgresql start/stop/status script | about 21 years ago |
| Started thread | pgsql: Create executor and planner-backend support for decoupled heap | about 21 years ago |
| Replied (other) | Bad n_distinct estimation; hacks suggested? | about 21 years ago |
| Replied (other) | Simplified (a-la [G|N]DBM) DB access | about 21 years ago |
| Replied (other) | Problem with PITR recovery | about 21 years ago |
| Started thread | Re: substring and POSIX re's | about 21 years ago |
| Replied (other) | Simplified (a-la [G|N]DBM) DB access | about 21 years ago |
| Replied (other) | Clarification | about 21 years ago |
| Replied (other) | Weirdess when altering serial column type | about 21 years ago |
| Replied (other) | Weirdess when altering serial column type | about 21 years ago |
| Replied (other) | pg_dump fails | about 21 years ago |
| Replied (other) | pg_dump fails | about 21 years ago |
| Replied (other) | Exception ERROR Code | about 21 years ago |
| Replied (other) | SETOF function call | about 21 years ago |
| Replied (other) | [WIP] shared locks | about 21 years ago |
| Started thread | pgsql: pg_dumpall should enforce the server version check for itself, | about 21 years ago |
| Started thread | pgsql: pg_dumpall should enforce the server version check for itself, | about 21 years ago |
| Replied (other) | Problem with PITR recovery | about 21 years ago |
| Replied (other) | pg_dump fails | about 21 years ago |
| Replied (other) | Plpgsql function with unknown number of args | about 21 years ago |
| Replied (other) | PostgreSQL as a filesystem | about 21 years ago |
| Replied (other) | increasingly slow insert/copy performance | about 21 years ago |
| Replied (other) | Problem with pgdump_all | about 21 years ago |
| Replied (other) | Comparing Datum's at aminsert() stage | about 21 years ago |
| Replied (other) | Urgent | about 21 years ago |
| Replied (other) | Urgent | about 21 years ago |
| Replied (own) | Assigning fixed OIDs to system catalogs and indexes | about 21 years ago |
| Replied (other) | Problem with PITR recovery | about 21 years ago |
| Replied (other) | 'Select INTO" in Execute (dynamic query ) | about 21 years ago |
| Replied (other) | Problem with PITR recovery | about 21 years ago |
| Replied (other) | BUG #1604: Composite types, triggers, and INET_CLIENT_ADDR() function | about 21 years ago |
| Started thread | pgsql: record_in and record_recv must be careful to return a separately | about 21 years ago |
| Started thread | pgsql: record_in and record_recv must be careful to return a separately | about 21 years ago |
| Replied (other) | Problem with PITR recovery | about 21 years ago |
| Replied (other) | Problem with PITR recovery | about 21 years ago |
| Replied (other) | Call to build-in operator from new operator | about 21 years ago |
| Replied (other) | Adding column in pg_proc | about 21 years ago |
| Replied (other) | How to get triggeroid by triggername in postgres 8.0 | about 21 years ago |
| Replied (other) | Exception handling: Oracle's "SQLERRM" keyword option? | about 21 years ago |