pgsql-general - August 2025

General discussion area for users. Apart from compile, acceptance test, and bug problems, most new users will probably only be interested in this mailing list (unless they want to contribute to development or documentation). All non-bug related questions regarding PostgreSQL's version of SQL, and all installation related questions that do not involve bugs or failed compiles, should be restricted to this area. Please note that many of the developers monitor this area.

Search the Archives

(enter a message-id to go directly to that message)

Browse Archives

Prev | Next

Aug. 1, 2025

Thread Author Time
Re: Failing to allocate memory when I think it shouldn't Christoph Moench-Tegeder 18:35

Aug. 2, 2025

Thread Author Time
Re: Get info about the index Igor Korot 00:06
Re: Get info about the index Adrian Klaver 00:13
Re: Get info about the index Jon Zeppieri 00:27
Re: Get info about the index Igor Korot 03:50
Re: Get info about the index Adrian Klaver 04:09

Aug. 4, 2025

Thread Author Time
Inquiry: Using PostgreSQL as a Staging Database for SAP ERP Data Export Ian Huang 01:47
What is the specific release date of PG18? 矫顺田 06:58
Re: What is the specific release date of PG18? David Rowley 07:54
Re: What is the specific release date of PG18? David G. Johnston 08:00
Re: What is the specific release date of PG18? David G. Johnston 08:00
PGDG16 repository error - repomd.xml.asc is empty Aleš Zelený 15:01
Re: PGDG16 repository error - repomd.xml.asc is empty Aleš Zelený 15:20

Aug. 5, 2025

Thread Author Time
Re: PGDG16 repository error - repomd.xml.asc is empty Aleš Zelený 08:05
Notices not printed by PQtrace Dominique Devienne 12:14
Re: Notices not printed by PQtrace Álvaro Herrera 13:17
Re: Notices not printed by PQtrace Dominique Devienne 14:19
Re: PGDG16 repository error - repomd.xml.asc is empty Adrian Klaver 15:04
Re: PGDG16 repository error - repomd.xml.asc is empty Aleš Zelený 15:25

Aug. 6, 2025

Thread Author Time
Re: analyze-in-stages post upgrade questions Mircea Cadariu 04:01
Stored procedures or raw queries Simon Connah 12:03
Re: Stored procedures or raw queries Justin Swanhart 12:07
Re: Stored procedures or raw queries Pavel Stehule 12:11
When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID 📎 Charles Qi 12:37
Re: Stored procedures or raw queries Philip Semanchuk 13:16
Libpq.dll [email protected] 13:17
Re: Stored procedures or raw queries Simon Connah 13:36
Re: Stored procedures or raw queries Dominique Devienne 13:42
Re: Stored procedures or raw queries Marco Torres 13:54
Re: analyze-in-stages post upgrade questions Fujii Masao 14:25
Re: Libpq.dll Adrian Klaver 17:46
CALL and named parameters Dominique Devienne 17:48
Re: CALL and named parameters Pavel Stehule 18:08
Re: CALL and named parameters Adrian Klaver 18:10
Re: analyze-in-stages post upgrade questions Nathan Bossart 18:14
Re: When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID Adrian Klaver 18:22
Re: Libpq.dll [email protected] 18:24
Re: Libpq.dll Merlin Moncure 19:28
Re: CALL and named parameters Christoph Moench-Tegeder 19:33
Re: Libpq.dll Adrian Klaver 20:02
Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Rumpi Gravenstein 20:17
Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Ron Johnson 20:25
Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Adrian Klaver 20:43
PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array David G. Johnston 20:43
Re: analyze-in-stages post upgrade questions Laurenz Albe 20:52
Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Rumpi Gravenstein 21:29
Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array David G. Johnston 21:35
Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Rumpi Gravenstein 21:39
Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Tom Lane 21:46

Aug. 7, 2025

Thread Author Time
Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array David G. Johnston 00:18
Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Adrian Klaver 01:15
Approach for DB migration Siraj G 01:29
Re: Approach for DB migration Ron Johnson 04:03
Re: Approach for DB migration Siraj G 04:21
Re: Approach for DB migration Ron Johnson 05:22
Re: Libpq.dll [email protected] 12:14
Re: CALL and named parameters Dominique Devienne 12:44
Re: CALL and named parameters David G. Johnston 13:30
Re: CALL and named parameters Pavel Stehule 14:16
Re: CALL and named parameters Dominique Devienne 14:18
Re: CALL and named parameters Tom Lane 14:21
Re: CALL and named parameters Dominique Devienne 14:26
Re: CALL and named parameters Tom Lane 14:36
Re: CALL and named parameters Dominique Devienne 14:39
Re: CALL and named parameters Tom Lane 14:42
Re: Libpq.dll Adrian Klaver 16:03
Re: CALL and named parameters Christoph Moench-Tegeder 23:14
Re: CALL and named parameters Tom Lane 23:33

Aug. 8, 2025

Thread Author Time
Re: When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID 📎 Charles Qi 01:20
Questions about the continuity of WAL archiving px shi 03:20
Re: Questions about the continuity of WAL archiving Adrian Klaver 04:25
Re: Questions about the continuity of WAL archiving px shi 05:50
Re: CALL and named parameters Dominique Devienne 08:18
Re: Libpq.dll [email protected] 12:55
Re: Questions about the continuity of WAL archiving Adrian Klaver 15:23
Re: Questions about the continuity of WAL archiving Greg Sabino Mullane 18:25
Re: Questions about the continuity of WAL archiving Ron Johnson 18:45
Re: When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID Adrian Klaver 22:43

Aug. 10, 2025

Thread Author Time
Re: Can postgres replication slot using pgoutput release multiple CDC records for a single update to a particular row Akashkiran Shivakumar 03:00
Re: Emitting JSON to file using COPY TO 📎 jian he 15:20
Re: When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID Laurenz Albe 19:34

Aug. 11, 2025

Thread Author Time
Re: When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID Charles Qi 03:34
Backups with filesystem snapshots Nick Cleaton 13:01
Re: Backups with filesystem snapshots Ron Johnson 13:13
Bitnami deprecation Smith 15:33
Re: Can postgres replication slot using pgoutput release multiple CDC records for a single update to a particular row Greg Sabino Mullane 15:37
Re: Bitnami deprecation Adrian Klaver 15:49
Re: Backups with filesystem snapshots Greg Sabino Mullane 16:41
Re: Inquiry: Using PostgreSQL as a Staging Database for SAP ERP Data Export Greg Sabino Mullane 16:49

Aug. 12, 2025

Thread Author Time
Re: Inquiry: Using PostgreSQL as a Staging Database for SAP ERP Data Export Ian Huang 00:10
Re: Questions about the continuity of WAL archiving px shi 08:24
Re: Questions about the continuity of WAL archiving px shi 08:33
Re: Questions about the continuity of WAL archiving px shi 08:37
Re: Bitnami deprecation Daniel Gustafsson 10:34
Re: Inquiry: Using PostgreSQL as a Staging Database for SAP ERP Data Export Ron Johnson 15:13
Re: Inquiry: Using PostgreSQL as a Staging Database for SAP ERP Data Export Adrian Klaver 16:04
Re: Questions about the continuity of WAL archiving Adrian Klaver 16:14
Re: Questions about the continuity of WAL archiving Bob Jolliffe 17:40
Re: Questions about the continuity of WAL archiving Ron Johnson 17:51
Re: Backups with filesystem snapshots Bruce Momjian 17:58
Re: Questions about the continuity of WAL archiving Adrian Klaver 19:19

Aug. 13, 2025

Thread Author Time
Re: Questions about the continuity of WAL archiving px shi 02:05
Re: Questions about the continuity of WAL archiving Ron Johnson 02:10
Re: Questions about the continuity of WAL archiving px shi 02:24
Re: Questions about the continuity of WAL archiving Justin 02:50
Re: When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID Laurenz Albe 05:14
Re: Questions about the continuity of WAL archiving px shi 05:48
pgbackrest check info fails without success KK CHN 07:35
Re: pgbackrest check info fails without success Ruben Morais 07:54
Re: pgbackrest check info fails without success KK CHN 08:52
Re: pgbackrest check info fails without success Ruben Morais 09:18
Re: pgbackrest check info fails without success KK CHN 11:23
Re: Bitnami deprecation Rachel Roch 12:47
help with upgrade from v15 to v16 rhel z/linux needed Evelina Angelova 12:54
Re: Questions about the continuity of WAL archiving Justin 14:05
Re: Questions about the continuity of WAL archiving Adrian Klaver 15:09

Aug. 14, 2025

Thread Author Time
Strange deadlock with object/target of lock : transaction Achilleas Mantzios 07:07
Re: help with upgrade from v15 to v16 rhel z/linux needed Adrian Klaver 14:29
Re: Strange deadlock with object/target of lock : transaction Adrian Klaver 14:39
Re: Strange deadlock with object/target of lock : transaction Achilleas Mantzios 15:01

Aug. 15, 2025

Thread Author Time
RE: help with upgrade from v15 to v16 rhel z/linux needed Evelina Angelova 06:49
Re: Questions about the continuity of WAL archiving Greg Sabino Mullane 16:40
Re: pgbackrest check info fails without success Greg Sabino Mullane 16:45

Aug. 18, 2025

Thread Author Time
Re: analyze-in-stages post upgrade questions Fujii Masao 02:36