| Replied (other) | rollback vs. commit for closing read-only transaction | about 21 years ago |
| Replied (other) | [proposal] protocol extension to support loadable stream filters | about 21 years ago |
| Replied (other) | Continue transactions after errors in psql | about 21 years ago |
| Replied (other) | Postgres 7.4.6 hang in async_notify | about 21 years ago |
| Started thread | pgsql: On further experimentation, there were still a couple of bugs in | about 21 years ago |
| Replied (other) | Bad n_distinct estimation; hacks suggested? | about 21 years ago |
| Started thread | pgsql: Fix ExpandIndirectionStar to handle cases where the expression to | about 21 years ago |
| Started thread | pgsql: get_expr_result_type probably needs to be able to handle OpExpr | about 21 years ago |
| Replied (other) | What does "tuple concurrently updated" mean? | about 21 years ago |
| Started thread | pgsql: Fix btree_gist to handle timetz zone correctly per recent | about 21 years ago |
| Replied (other) | DDL from psql console? | about 21 years ago |
| Replied (other) | timezone() with timeofday() converts the wrong direction? | about 21 years ago |
| Replied (other) | pgsql: Re-add item with better description: > * Allow ORDER BY ... | about 21 years ago |
| Replied (other) | Bad n_distinct estimation; hacks suggested? | about 21 years ago |
| Replied (other) | What does "tuple concurrently updated" mean? | about 21 years ago |
| Replied (other) | How to make lazy VACUUM of one table run in several transactions ? | about 21 years ago |
| Replied (other) | simplify register_dirty_segment() | about 21 years ago |
| Replied (other) | timezone() with timeofday() converts the wrong direction? | about 21 years ago |
| Started thread | pgsql: Fix btree_gist to handle timetz zone correctly per recent | about 21 years ago |
| Replied (other) | CVS regression test problem | about 21 years ago |
| Replied (other) | Bad n_distinct estimation; hacks suggested? | about 21 years ago |
| Started thread | pgsql: Avoid rechecking lossy operators twice in a bitmap scan plan. | about 21 years ago |
| Started thread | pgsql: While determining the filter clauses for an index scan (either | about 21 years ago |
| Replied (own) | Old-style OR indexscan slated for destruction | about 21 years ago |
| Started thread | pgsql: Replace slightly klugy create_bitmap_restriction() function with | about 21 years ago |
| Started thread | pgsql: Remove support for OR'd indexscans internal to a single IndexScan | about 21 years ago |