Filter:

Messages on April 25, 2005

Threads26 messages
9Started
1Replied in own
16Replied to othersin 12 threads
Patchesnone in this period
0New patchfirst in its thread
0Follow-uprevision of an earlier one
ActivityThreadSent
Replied (other)rollback vs. commit for closing read-only transactionover 21 years ago
Replied (other)[proposal] protocol extension to support loadable stream filtersover 21 years ago
Replied (other)Continue transactions after errors in psqlover 21 years ago
Replied (other)Postgres 7.4.6 hang in async_notifyover 21 years ago
Started threadpgsql: On further experimentation, there were still a couple of bugs inover 21 years ago
Replied (other)Bad n_distinct estimation; hacks suggested?over 21 years ago
Started threadpgsql: Fix ExpandIndirectionStar to handle cases where the expression toover 21 years ago
Started threadpgsql: get_expr_result_type probably needs to be able to handle OpExprover 21 years ago
Replied (other)What does "tuple concurrently updated" mean?over 21 years ago
Started threadpgsql: Fix btree_gist to handle timetz zone correctly per recentover 21 years ago
Replied (other)DDL from psql console?over 21 years ago
Replied (other)timezone() with timeofday() converts the wrong direction?over 21 years ago
Replied (other)pgsql: Re-add item with better description: > * Allow ORDER BY ...over 21 years ago
Replied (other)Bad n_distinct estimation; hacks suggested?over 21 years ago
Replied (other)What does "tuple concurrently updated" mean?over 21 years ago
Replied (other)How to make lazy VACUUM of one table run in several transactions ?over 21 years ago
Replied (other)simplify register_dirty_segment()over 21 years ago
Replied (other)timezone() with timeofday() converts the wrong direction?over 21 years ago
Started threadpgsql: Fix btree_gist to handle timetz zone correctly per recentover 21 years ago
Replied (other)CVS regression test problemover 21 years ago
Replied (other)Bad n_distinct estimation; hacks suggested?over 21 years ago
Started threadpgsql: Avoid rechecking lossy operators twice in a bitmap scan plan.over 21 years ago
Started threadpgsql: While determining the filter clauses for an index scan (eitherover 21 years ago
Replied (own)Old-style OR indexscan slated for destructionover 21 years ago
Started threadpgsql: Replace slightly klugy create_bitmap_restriction() function withover 21 years ago
Started threadpgsql: Remove support for OR'd indexscans internal to a single IndexScanover 21 years ago