Mailing lists [pgsql-bugs]
- Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned Michael Paquier
- Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index Michael Paquier
- Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index Tom Lane
- Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned Tom Lane
- Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned Michael Paquier
- Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned Tom Lane
- Bug in postgresql related column level security authentication. Shubham Gholap
- Re: Help pg_restore version Euler Taveira
- Re: BUG #18141: sorry, too many clients error occurring very frequently Joe Conway
- Re: Help pg_restore version Jorge Soro Domenech
- Re: Help pg_restore version Jorge Soro Domenech
- Re: Help pg_restore version Tom Lane
- Re: Bug in postgresql related column level security authentication. Tom Lane
- Re: Help pg_restore version Jorge Soro Domenech
- Re: BUG #18141: sorry, too many clients error occurring very frequently Tom Lane
- Re: BUG #18141: sorry, too many clients error occurring very frequently Joe Conway
- Re: BUG #18141: sorry, too many clients error occurring very frequently Tom Lane
- Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned Michael Paquier
- Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index Michael Paquier
- Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index Tom Lane
- BUG #18142: strange behaviour of "UPDATE" with id_encode() PG Bug reporting form
- Re: BUG #18129: GiST index produces incorrect query results Heikki Linnakangas
- BUG #18143: pg_upgrade fails to use port 50432 even with firewall disabled PG Bug reporting form
- Re: BUG #18142: strange behaviour of "UPDATE" with id_encode() Tom Lane
- BUG #18142: strange behaviour of "UPDATE" with id_encode() David G. Johnston
- BUG #18144: While i am intalling postgresql-12 repo,i am facing the below.i tried with dowload and install. PG Bug reporting form
- Re: pg_restore 14 skips ACL COLUMN when --schema is used Tom Lane
- Re: BUG #18142: strange behaviour of "UPDATE" with id_encode() DataSelfService Srl
- BUG #18145: In psql, \d does not output in expanded format PG Bug reporting form
- Re: BUG #18145: In psql, \d does not output in expanded format Laurenz Albe
- Re: BUG #18144: While i am intalling postgresql-12 repo,i am facing the below.i tried with dowload and install. Laurenz Albe
- BUG ERROR: COULDN´T ACCESS THE URL Priscilla Riggioni Leonhardes
- BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows PG Bug reporting form
- Re: pg_rewind: ERROR: could not fetch remote file "global/pg_control": ERROR: permission denied Zhaoxun Yan
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Laurenz Albe
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Michael Paquier
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Tom Lane
- REFRESH MATERIALIZED VIEW error Given, Robert A
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Thomas Munro
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Thomas Munro
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Michael Paquier
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Tom Lane
- Re: REFRESH MATERIALIZED VIEW error Tom Lane
- Re: [16+] subscription can end up in inconsistent state Peter Smith
- Re: [16+] subscription can end up in inconsistent state vignesh C
- BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx PG Bug reporting form
- RE: REFRESH MATERIALIZED VIEW error Given, Robert A
- BUG #18148: Handle null in a date/time fields when passing empty arrays issue PG Bug reporting form
- Re: BUG #18148: Handle null in a date/time fields when passing empty arrays issue David G. Johnston
- Re: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx David G. Johnston
- Re: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Tom Lane
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Thomas Munro
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Thomas Munro
- BUG #18149: Incorrect lexeme for english token "proxy" PG Bug reporting form
- Re: [16+] subscription can end up in inconsistent state Peter Smith
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Thomas Munro
- Re: [16+] subscription can end up in inconsistent state vignesh C
- Re: [16+] subscription can end up in inconsistent state Peter Smith
- Re: BUG #17821: Assertion failed in heap_update() due to heap pruning Alexander Lakhin
- Re: BUG #18149: Incorrect lexeme for english token "proxy" Laurenz Albe
- Re: BUG #18149: Incorrect lexeme for english token "proxy" Tom Lane
- Re: BUG #18149: Incorrect lexeme for english token "proxy" Patrick Peralta
- Re: BUG #18149: Incorrect lexeme for english token "proxy" Tom Lane
- Re: BUG #18149: Incorrect lexeme for english token "proxy" Patrick Peralta
- Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower Richard Guo
- AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Hans Buschmann
- Re: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Tom Lane
- Access to old versions of a row Matthias Apitz
- BUG #18150: The results returned by index only scan using gist index of bpchar and seqscan have difference. PG Bug reporting form
- Re: BUG #18150: The results returned by index only scan using gist index of bpchar and seqscan have difference. Tom Lane
- BUG #18151: pg_upgradecluster fails when column default refers to column PG Bug reporting form
- Re: Access to old versions of a row Vik Fearing
- Re: EXPLAIN Verbose issue - custom_scan_tlist can directly refer CTE and Subquery Andrei Lepikhov
- Re: Access to old versions of a row Alvaro Herrera
- Re: BUG #18151: pg_upgradecluster fails when column default refers to column Tom Lane
- Re: BUG #18151: pg_upgradecluster fails when column default refers to column David G. Johnston
- Re: BUG #18151: pg_upgradecluster fails when column default refers to column Tom Lane
- Re: BUG #18151: pg_upgradecluster fails when column default refers to column Liam Morland
- Re: BUG #18151: pg_upgradecluster fails when column default refers to column Tom Lane
- Re: Access to old versions of a row Andres Freund
- BUG #18152: Join condition is not pushed down to union all subquery PG Bug reporting form
- Re: pg_rewind: ERROR: could not fetch remote file "global/pg_control": ERROR: permission denied Zhaoxun Yan
- BUG #18153: Undefined Symbol creating postgis_raster extension PG Bug reporting form
- Re: EXPLAIN Verbose issue - custom_scan_tlist can directly refer CTE and Subquery a.rybakina
- Re: BUG #18153: Undefined Symbol creating postgis_raster extension Laurenz Albe
- Re: BUG #18152: Join condition is not pushed down to union all subquery Tom Lane
- Re: FW: Query execution failure Bruce Momjian
- BUG #18154: Corrupt DB: pg_dump segfaults or returns empty PG Bug reporting form
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Robert Haas
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Robert Haas
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Thomas Munro
- Re: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used Tom Lane
- BUG #18155: Logical Apply Worker Timeout During TableSync Causes Either Stuckness or Data Loss PG Bug reporting form
- Re: BUG #18155: Logical Apply Worker Timeout During TableSync Causes Either Stuckness or Data Loss Amit Kapila
- BUG #18156: Self-referential foreign key in partitioned table not enforced on deletes PG Bug reporting form
- Re: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used Alexander Lakhin
- Re: BUG #18130: \copy fails with "could not read block" or "page should be empty but not" errors due to triggers Andres Freund
- Re: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used Alexander Lakhin
- System administration functions about relation size ignore changes in the table structure Erki Eessaar
- Re: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used Tom Lane
- Re: System administration functions about relation size ignore changes in the table structure Tom Lane
- Re: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used Tom Lane
- Re: System administration functions about relation size ignore changes in the table structure Erki Eessaar
- Re: System administration functions about relation size ignore changes in the table structure David G. Johnston
- Re: System administration functions about relation size ignore changes in the table structure Tom Lane
- Re: BUG #18152: Join condition is not pushed down to union all subquery Richard Guo
- BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending PG Bug reporting form
- Assert failure when CREATE TEMP TABLE Richard Guo
- Re: Assert failure when CREATE TEMP TABLE Tom Lane
- BUG #18159: Database Integrity Concerns: Missing FK Constraint PG Bug reporting form
- Re: BUG #18155: Logical Apply Worker Timeout During TableSync Causes Either Stuckness or Data Loss Callahan, Drew
- Re: BUG #18159: Database Integrity Concerns: Missing FK Constraint Laurenz Albe
- Re: BUG #18155: Logical Apply Worker Timeout During TableSync Causes Either Stuckness or Data Loss Amit Kapila
- Error “Unable to Write Inside Temp Environment Variable Path” Le Thai Hoa
- Re: Assert failure when CREATE TEMP TABLE Alexander Lakhin
- Re: Error “Unable to Write Inside Temp Environment Variable Path” Laurenz Albe
- Re: BUG #18155: Logical Apply Worker Timeout During TableSync Causes Either Stuckness or Data Loss Michael Paquier
- Re: Assert failure when CREATE TEMP TABLE Richard Guo
- Insufficient memory access checks in pglz_decompress Flavien GUEDEZ
- Re: Insufficient memory access checks in pglz_decompress Tom Lane
- Re: Insufficient memory access checks in pglz_decompress Flavien GUEDEZ
- BUG #18160: first create table show "ERROR: permission denied for schema public", next create table works PG Bug reporting form
- BUG #18161: ALTER TABLE ... ALTER COLUMN does not remove dependencies in automatically from column and sequence. PG Bug reporting form
- Variable substitution in jsonb functions fails for jsonpath operator like_regex Erwin Brandstetter
- Re: BUG #18161: ALTER TABLE ... ALTER COLUMN does not remove dependencies in automatically from column and sequence. Laurenz Albe
- Re: BUG #18161: ALTER TABLE ... ALTER COLUMN does not remove dependencies in automatically from column and sequence. Anthony Sotolongo
- Re: BUG #18160: first create table show "ERROR: permission denied for schema public", next create table works Laurenz Albe
- Re: BUG #18160: first create table show "ERROR: permission denied for schema public", next create table works Laurenz Albe
- Re: BUG #18160: first create table show "ERROR: permission denied for schema public", next create table works Laurenz Albe
- Re: Variable substitution in jsonb functions fails for jsonpath operator like_regex Tom Lane
- Re: Variable substitution in jsonb functions fails for jsonpath operator like_regex Jeff Janes
- Re: Insufficient memory access checks in pglz_decompress Tom Lane
- Re: Variable substitution in jsonb functions fails for jsonpath operator like_regex Tom Lane
- Re: Variable substitution in jsonb functions fails for jsonpath operator like_regex David G. Johnston
- Re: Invalid dump file after drop of role that previously created extension containing a table. Aleš Zelený
- Re: Insufficient memory access checks in pglz_decompress Flavien GUEDEZ
- Re: group by true now errors with non-integer constant in GROUP BY Dennis Brouwer
- Re: group by true now errors with non-integer constant in GROUP BY Laurenz Albe
- Re: group by true now errors with non-integer constant in GROUP BY David G. Johnston
- Re: Variable substitution in jsonb functions fails for jsonpath operator like_regex Tom Lane
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Robert Haas
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Thomas Munro
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Thomas Munro
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Thomas Munro
- Re: group by true now errors with non-integer constant in GROUP BY Vik Fearing
- Re: group by true now errors with non-integer constant in GROUP BY Vik Fearing
- Re: group by true now errors with non-integer constant in GROUP BY Laurenz Albe
- BUG #18163: Catcache entry invalidation might be missed when toast processed inside CatalogCacheCreateEntry PG Bug reporting form
- slow pg_dump with bytea Janning Vygen
- Re: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used Alexander Lakhin
- Re: slow pg_dump with bytea Laurenz Albe
- Re: slow pg_dump with bytea Janning Vygen
- Re: slow pg_dump with bytea Laurenz Albe
- Re: slow pg_dump with bytea Alvaro Herrera
- Re: group by true now errors with non-integer constant in GROUP BY Tom Lane
- BUG #18165: Could not duplicate handle for "Global/PostgreSQL.xxxxxxxxxx": Bad file descriptor PG Bug reporting form
- BUG #18166: 100 Gb 18000000 records table update PG Bug reporting form
- Re: BUG #18165: Could not duplicate handle for "Global/PostgreSQL.xxxxxxxxxx": Bad file descriptor Tom Lane
- Re: BUG #18165: Could not duplicate handle for "Global/PostgreSQL.xxxxxxxxxx": Bad file descriptor Andres Freund
- Re: BUG #18165: Could not duplicate handle for "Global/PostgreSQL.xxxxxxxxxx": Bad file descriptor Tom Lane
- Re: BUG #18166: 100 Gb 18000000 records table update Tom Lane
- Re: BUG #18165: Could not duplicate handle for "Global/PostgreSQL.xxxxxxxxxx": Bad file descriptor Thomas Munro
- Re: BUG #18165: Could not duplicate handle for "Global/PostgreSQL.xxxxxxxxxx": Bad file descriptor Thomas Munro
- Re: BUG #18165: Could not duplicate handle for "Global/PostgreSQL.xxxxxxxxxx": Bad file descriptor Thomas Munro
- Re: BUG #18165: Could not duplicate handle for "Global/PostgreSQL.xxxxxxxxxx": Bad file descriptor Alexander Lakhin
- Re[2]: BUG #18166: 100 Gb 18000000 records table update Ruslan Ganeev
- RE: BUG #18165: Could not duplicate handle for "Global/PostgreSQL.xxxxxxxxxx": Bad file descriptor Boyer, Maxime (he/him | il/lui)
- Re: BUG #18165: Could not duplicate handle for "Global/PostgreSQL.xxxxxxxxxx": Bad file descriptor Thomas Munro
- Re: BUG #17893: Assert failed in heap_update()/_delete() when FK modiified by RI trigger in non-read-committed xact Alexander Lakhin
- Re: BUG #18155: Logical Apply Worker Timeout During TableSync Causes Either Stuckness or Data Loss Michael Paquier
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Robert Haas
- AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Hans Buschmann
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Tom Lane
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Peter Geoghegan
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Tom Lane
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Peter Geoghegan
- Re: BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25 shihao zhong
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Tom Lane
- Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Thomas Munro
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Peter Geoghegan
- Re: Variable substitution in jsonb functions fails for jsonpath operator like_regex Erwin Brandstetter
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Tom Lane
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Peter Geoghegan
- Re: Variable substitution in jsonb functions fails for jsonpath operator like_regex Tom Lane
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Tom Lane
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Peter Geoghegan
- Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower Andrei Lepikhov
- AW: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Hans Buschmann
- BUG #18167: cannot create partitioned tables when default_tablespace is set PG Bug reporting form
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Amit Langote
- Re: BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25 Alexander Lakhin
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Tom Lane
- Re: AW: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Tom Lane
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Tom Lane
- RE: BUG #18165: Could not duplicate handle for "Global/PostgreSQL.xxxxxxxxxx": Bad file descriptor Boyer, Maxime (he/him | il/lui)
- BUG #18168: Parallel worker failed to initialize: could not create inherited socket: error code 10106 PG Bug reporting form
- RE: BUG #18168: Parallel worker failed to initialize: could not create inherited socket: error code 10106 Boyer, Maxime (he/him | il/lui)
- Re: BUG #18167: cannot create partitioned tables when default_tablespace is set Alvaro Herrera
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Amit Langote
- Re: BUG #18167: cannot create partitioned tables when default_tablespace is set tender wang
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Tom Lane
- Re: BUG #18168: Parallel worker failed to initialize: could not create inherited socket: error code 10106 Tom Lane
- RE: BUG #18168: Parallel worker failed to initialize: could not create inherited socket: error code 10106 Boyer, Maxime (he/him | il/lui)
- missing requirement on ccache in postgresql16-devel Greg Hennessy
- Re: missing requirement on ccache in postgresql16-devel Bruce Momjian
- Re: missing requirement on ccache in postgresql16-devel Tom Lane
- Re: missing requirement on ccache in postgresql16-devel Bruce Momjian
- Re: BUG #18168: Parallel worker failed to initialize: could not create inherited socket: error code 10106 Thomas Munro
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Amit Langote
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Tom Lane
- Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx Amit Langote
- BUG #18170: Unexpected error: no relation entry for relid 3 PG Bug reporting form
- BUG #18171: Dropping an index on a partitioned table drops all child indices even with a restrict PG Bug reporting form
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Vik Fearing
- Re: BUG #18171: Dropping an index on a partitioned table drops all child indices even with a restrict David G. Johnston
- Re: BUG #18171: Dropping an index on a partitioned table drops all child indices even with a restrict Nicholas Dujay
- Re: BUG #18171: Dropping an index on a partitioned table drops all child indices even with a restrict David G. Johnston
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Tom Lane
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Alexander Korotkov
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Alexander Korotkov
- Re: missing requirement on ccache in postgresql16-devel Devrim Gündüz
- Re: missing requirement on ccache in postgresql16-devel Bruce Momjian
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Andrei Lepikhov
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Alexander Korotkov
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Andrei Lepikhov
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Andrei Lepikhov
- BUG #18172: High memory usage in tSRF function context PG Bug reporting form
- Logical replication is missing block of rows when sending initial sync? hubert depesz lubaczewski
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Richard Guo
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Tom Lane
- Re: missing requirement on ccache in postgresql16-devel Greg Hennessy
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Alexander Korotkov
- Re: BUG #18172: High memory usage in tSRF function context Tom Lane
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Andrei Lepikhov
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Vik Fearing
- Re:BUG #18172: High memory usage in tSRF function context Sergei Kornilov
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Alexander Korotkov
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Andrei Lepikhov
- Re: COPY TO CSV produces data that is incompatible/unsafe for \COPY FROM CSV Bruce Momjian
- Re: BUG #18172: High memory usage in tSRF function context Tom Lane
- Re:BUG #18172: High memory usage in tSRF function context Sergei Kornilov
- Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly Bruce Momjian
- Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly Tom Lane
- Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly Pavel Borisov
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Alexander Korotkov
- Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly Bruce Momjian
- Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly Bruce Momjian
- Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly Tom Lane
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Tom Lane
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Richard Guo
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Richard Guo
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Andrei Lepikhov
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Andrei Lepikhov
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Richard Guo
- RE: Logical replication is missing block of rows when sending initial sync? Hayato Kuroda (Fujitsu)
- Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly Bruce Momjian
- BUG #18173: ERROR: could not identify a comparison function for type iso-8859-1 PG Bug reporting form
- Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly Tom Lane
- Re: Logical replication is missing block of rows when sending initial sync? hubert depesz lubaczewski
- Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly Bruce Momjian
- Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly Tom Lane
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Andrei Lepikhov
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Richard Guo
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Richard Guo
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Alexander Korotkov
- Re: BUG #18170: Unexpected error: no relation entry for relid 3 Alexander Korotkov
- Re: BUG #18173: ERROR: could not identify a comparison function for type iso-8859-1 Laurenz Albe
- 回复: BUG #18173: ERROR: could not identify a comparison function for type unknown 下雨天
- Re: BUG #18173: ERROR: could not identify a comparison function for type iso-8859-1 Tom Lane