pgsql-general  

Messages by Thread

• PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Rumpi Gravenstein
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Adrian Klaver
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Tom Lane
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Rumpi Gravenstein
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Adrian Klaver
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Rumpi Gravenstein
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Tom Lane
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Rumpi Gravenstein
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Tom Lane
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Tom Lane
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Laurenz Albe
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Tom Lane
• Upper / lower case keys in JSON objects Mark
  • Re: Upper / lower case keys in JSON objects Mark
  • Re: Upper / lower case keys in JSON objects Adrian Klaver
• Sorting by respecting diacritics/accents JānisE
  • Re: Sorting by respecting diacritics/accents Laurenz Albe
• Re: Is there any limit on the number of rows to import using copy command sivapostg...@yahoo.com
  • Re: Is there any limit on the number of rows to import using copy command Laurenz Albe
  • Re: Is there any limit on the number of rows to import using copy command sivapostg...@yahoo.com
  • Re: Is there any limit on the number of rows to import using copy command Laurenz Albe
  • Re: Is there any limit on the number of rows to import using copy command sivapostg...@yahoo.com
  • Re: Is there any limit on the number of rows to import using copy command David Barbour
  • Re: Is there any limit on the number of rows to import using copy command Adrian Klaver
  • Re: Is there any limit on the number of rows to import using copy command Merlin Moncure
  • Re: Is there any limit on the number of rows to import using copy command sivapostg...@yahoo.com
  • Re: Is there any limit on the number of rows to import using copy command Adrian Klaver
  • Re: Is there any limit on the number of rows to import using copy command sivapostg...@yahoo.com
  • Re: Is there any limit on the number of rows to import using copy command Ron Johnson
  • Re: Is there any limit on the number of rows to import using copy command Adrian Klaver
• Wrapping a select in another select makes it slower Peter J. Holzer
  • Re: Wrapping a select in another select makes it slower David Rowley
  • Re: Wrapping a select in another select makes it slower Peter J. Holzer
• Postgresql 16.9 fast shutdown hangs with walsenders eating 100% CPU Klaus Darilion
  • Re: Postgresql 16.9 fast shutdown hangs with walsenders eating 100% CPU Laurenz Albe
• Possible causes of high_replay lag, given replication settings? Jon Zeppieri
  • Re: Possible causes of high_replay lag, given replication settings? Nick Cleaton
  • Re: Possible causes of high_replay lag, given replication settings? Jon Zeppieri
  • Re: Possible causes of high_replay lag, given replication settings? Greg Sabino Mullane
• PgBouncer Prepared Statement ERROR KK CHN
  • Re: PgBouncer Prepared Statement ERROR Greg Sabino Mullane
  • Re: PgBouncer Prepared Statement ERROR Laurenz Albe
  • Re: PgBouncer Prepared Statement ERROR Achilleas Mantzios
• Regarding logical replication issues with PostgreSQL versions 16 and above yexiu-glory
  • Re: Regarding logical replication issues with PostgreSQL versions 16 and above Laurenz Albe
• Should we document the cost of pg_database_size()? Alternatives? Craig Ringer
  • Re: Should we document the cost of pg_database_size()? Alternatives? Craig Ringer
  • Re: Should we document the cost of pg_database_size()? Alternatives? Ron Johnson
• PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Laurenz Albe
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Nico Williams
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Seref Arikan
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Seref Arikan
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Nico Williams
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Jeff Ross
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Marco Torres
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
• PgBouncer-Postgres : un supported startup parameter statement_timeout KK CHN
  • Re: PgBouncer-Postgres : un supported startup parameter statement_timeout Achilleas Mantzios
  • Re: PgBouncer-Postgres : un supported startup parameter statement_timeout Achilleas Mantzios
  • Re: PgBouncer-Postgres : un supported startup parameter statement_timeout Adrian Klaver
  • Re: PgBouncer-Postgres : un supported startup parameter statement_timeout Robert Sjöblom
• Removing terminal period from varchar string in table column Rich Shepard
  • Re: Removing terminal period from varchar string in table column Jeff Ross
  • Re: Removing terminal period from varchar string in table column Rich Shepard
  • Re: Removing terminal period from varchar string in table column Thom Brown
  • Re: Removing terminal period from varchar string in table column Rich Shepard
  • Re: Removing terminal period from varchar string in table column Thom Brown
  • Re: Removing terminal period from varchar string in table column Rich Shepard
• Regarding query optimisation (select for update) Durgamahesh Manne
  • Re: Regarding query optimisation (select for update) Laurenz Albe
  • Re: Regarding query optimisation (select for update) Durgamahesh Manne
  • Re: Regarding query optimisation (select for update) Laurenz Albe
  • Re: Regarding query optimisation (select for update) Tom Lane
  • Re: Regarding query optimisation (select for update) Greg Sabino Mullane
  • Re: Regarding query optimisation (select for update) Andy Huang
• Performance of JSON type in postgres veem v
  • Re: Performance of JSON type in postgres Adrian Klaver
  • Re: Performance of JSON type in postgres David G. Johnston
  • Re: Performance of JSON type in postgres Merlin Moncure
  • Re: Performance of JSON type in postgres veem v
  • Re: Performance of JSON type in postgres Adrian Klaver
  • Re: Performance of JSON type in postgres veem v
  • Re: Performance of JSON type in postgres Ron Johnson
  • Re: Performance of JSON type in postgres Adrian Klaver
• Syntax error needs explanation Rich Shepard
  • Re: Syntax error needs explanation David G. Johnston
  • Re: Syntax error needs explanation [RESOLVED] Rich Shepard
  • Re: Syntax error needs explanation [RESOLVED] Laurenz Albe
  • Re: Syntax error needs explanation [RESOLVED] David G. Johnston
  • Re: Syntax error needs explanation [RESOLVED] Rich Shepard
  • Re: Syntax error needs explanation Adrian Klaver
  • Re: Syntax error needs explanation Adrian Klaver
  • Re: Syntax error needs explanation David G. Johnston
  • Re: Syntax error needs explanation Rich Shepard
  • Re: Syntax error needs explanation David G. Johnston
  • Re: Syntax error needs explanation [RESOLVED] Rich Shepard
• Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Amol Inamdar
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Laurenz Albe
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Amol Inamdar
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Laurenz Albe
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Amol Inamdar
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Laurenz Albe
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Amol Inamdar
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Tom Lane
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Peter J. Holzer
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Tom Lane
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Benjamin Wang
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) David G. Johnston
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Tom Lane
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Laurenz Albe
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Amol Inamdar
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Amol Inamdar
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Ron Johnson
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Laurenz Albe
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Amol Inamdar
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Tom Lane
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Greg Sabino Mullane
  • Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) Ron Johnson
• Query regarding support of test_decoding and PGReplicationStream with Standby Logical Replication Kiran K V
  • Query regarding support of test_decoding and PGReplicationStream with Standby Logical Replication Kiran K V
  • Re: Query regarding support of test_decoding and PGReplicationStream with Standby Logical Replication DINESH NAIR
  • Re: Query regarding support of test_decoding and PGReplicationStream with Standby Logical Replication Kiran K V
• I have a suspicious query Edmundo Robles
  • Re: I have a suspicious query Adrian Klaver
  • Re: I have a suspicious query Greg Sabino Mullane
  • Re: I have a suspicious query Ron Johnson
  • Re: I have a suspicious query Merlin Moncure
  • Re: I have a suspicious query Matthias Apitz
• Question Regarding COPY Command Handling of Line Breaks in PostgreSQL gzh
  • Re: Question Regarding COPY Command Handling of Line Breaks in PostgreSQL Ron Johnson
  • Re: Question Regarding COPY Command Handling of Line Breaks in PostgreSQL Adrian Klaver
  • Re:Question Regarding COPY Command Handling of Line Breaks in PostgreSQL gzh
• optimizing number of workers Greg Hennessy
  • Re: optimizing number of workers Weck, Luis
  • Re: optimizing number of workers Greg Hennessy
  • Re: optimizing number of workers Tom Lane
  • Re: optimizing number of workers Greg Hennessy
• having temp_tablespaces on less reliable storage Dimitrios Apostolou
  • Re: having temp_tablespaces on less reliable storage David G. Johnston
  • Re: having temp_tablespaces on less reliable storage Dimitrios Apostolou
  • Re: having temp_tablespaces on less reliable storage Ron Johnson
• Lock timeout in commit Steve Baldwin
  • Re: Lock timeout in commit Tom Lane
  • Re: Lock timeout in commit Steve Baldwin
• Aggregate versions of hashing functions (md5, sha1, etc...) Dominique Devienne
  • Re: Aggregate versions of hashing functions (md5, sha1, etc...) Adrian Klaver
  • Re: Aggregate versions of hashing functions (md5, sha1, etc...) Ron Johnson
  • Re: Aggregate versions of hashing functions (md5, sha1, etc...) Dominique Devienne
  • Re: Aggregate versions of hashing functions (md5, sha1, etc...) Ron Johnson
  • Re: Aggregate versions of hashing functions (md5, sha1, etc...) Dominique Devienne
  • Re: Aggregate versions of hashing functions (md5, sha1, etc...) Dominique Devienne
  • Re: Aggregate versions of hashing functions (md5, sha1, etc...) Adrian Klaver
  • Re: Aggregate versions of hashing functions (md5, sha1, etc...) Florents Tselai
  • Re: Aggregate versions of hashing functions (md5, sha1, etc...) Adrian Klaver
  • Re: Aggregate versions of hashing functions (md5, sha1, etc...) Dominique Devienne
  • Re: Aggregate versions of hashing functions (md5, sha1, etc...) Merlin Moncure
  • Re: Aggregate versions of hashing functions (md5, sha1, etc...) Adrian Klaver
  • Re: Aggregate versions of hashing functions (md5, sha1, etc...) Merlin Moncure
  • Re: Aggregate versions of hashing functions (md5, sha1, etc...) Merlin Moncure
  • Re: Aggregate versions of hashing functions (md5, sha1, etc...) Dominique Devienne
• PostgresSQL Setup error Jordan Adams
  • Re: PostgresSQL Setup error Laurenz Albe
  • Re: PostgresSQL Setup error Adrian Klaver
  • Re: PostgresSQL Setup error DINESH NAIR
• Password Encryption and Connection Issues Alpaslan AKDAĞ
  • Re: Password Encryption and Connection Issues David G. Johnston
  • Re: Password Encryption and Connection Issues Greg Sabino Mullane
  • Re: Password Encryption and Connection Issues Ron Johnson
  • Re: Password Encryption and Connection Issues David G. Johnston
  • Re: Password Encryption and Connection Issues Ron Johnson
  • Re: Password Encryption and Connection Issues Laurenz Albe
  • Re: Password Encryption and Connection Issues Greg Sabino Mullane
  • Re: Password Encryption and Connection Issues Adrian Klaver
  • Re: Password Encryption and Connection Issues Ron Johnson
• error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin abrahim abrahao
  • Re: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin Shlok Kyal
  • Re: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin Shlok Kyal
  • RE: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin Hayato Kuroda (Fujitsu)
  • Re: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin abrahim abrahao
  • RE: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin Hayato Kuroda (Fujitsu)
  • Re: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin abrahim abrahao
  • RE: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin Hayato Kuroda (Fujitsu)
• Logical Replication 08P01 invalid memory alloc request size 1095736448 Soni M
  • Re: Logical Replication 08P01 invalid memory alloc request size 1095736448 Soni M
  • Re: Logical Replication 08P01 invalid memory alloc request size 1095736448 Tom Lane
  • Re: Logical Replication 08P01 invalid memory alloc request size 1095736448 Soni M
• pg_upgrade: can I use same binary for old & new? Pierre Fortin
  • Re: pg_upgrade: can I use same binary for old & new? David G. Johnston
  • Re: pg_upgrade: can I use same binary for old & new? Tom Lane

• Earlier messages