Filter:

Messages on August 27, 2020

Threads15 messages
7Started
0Replied in own
8Replied to othersin 7 threads
Patchesnone in this period
0New patchfirst in its thread
0Follow-uprevision of an earlier one
ActivityThreadSent
Started threadpgsql: Fix code for re-finding scan position in a multicolumn GIN indexabout 6 years ago
Started threadpgsql: Fix code for re-finding scan position in a multicolumn GIN indexabout 6 years ago
Started threadpgsql: Fix code for re-finding scan position in a multicolumn GIN indexabout 6 years ago
Started threadpgsql: Fix code for re-finding scan position in a multicolumn GIN indexabout 6 years ago
Started threadpgsql: Fix code for re-finding scan position in a multicolumn GIN indexabout 6 years ago
Started threadpgsql: Fix code for re-finding scan position in a multicolumn GIN indexabout 6 years ago
Started threadpgsql: Fix code for re-finding scan position in a multicolumn GIN indexabout 6 years ago
Replied (other)BUG #16595: Reads fail with "lost saved point in index" error after writesabout 6 years ago
Replied (other)could not send data to client: Permission deniedabout 6 years ago
Replied (other)Deprecating postfix and factorial operators in PostgreSQL 13about 6 years ago
Replied (other)Clang Address Sanitizer (Postgres14) Detected Memory Leaksabout 6 years ago
Replied (other)BUG #16595: Reads fail with "lost saved point in index" error after writesabout 6 years ago
Replied (other)factorial function/phase out postfix operators?about 6 years ago
Replied (other)Are advisory locks guaranteed to be First Come First Serve? And can the behavior be relied upon?about 6 years ago
Replied (other)How is bushy plans generated in join_search_one_levabout 6 years ago