agora inbox for pgsql-admin@postgresql.org
help / color / mirror / Atom feedSeeking Recommendations for PostgreSQL Backup, Restore, and Upgrade Strategy
2026-09-08 10:20 UTC Cipriani, Ivan <ivan.cipriani@gehealthcare.com>
` Re: Seeking Recommendations for PostgreSQL Backup, Restore, and Upgrade Strategy
2026-09-09 11:13 UTC Ron Johnson <ronljohnsonjr@gmail.com>
` Re: Seeking Recommendations for PostgreSQL Backup, Restore, and Upgrade Strategy
2026-09-09 11:16 UTC Muhammed Ali Demirci <dmrc.muhammedali@gmail.com>
` Re: Seeking Recommendations for PostgreSQL Backup, Restore, and Upgrade Strategy
2026-09-09 11:55 UTC Paul Smith <paul@pscs.co.uk>
` Re: Seeking Recommendations for PostgreSQL Backup, Restore, and Upgrade Strategy
2026-09-09 18:45 UTC gunnar wagner <vrms@netcologne.de>
[5+ messages in thread]
current stable version for oracle linux 8 and 9
2026-09-09 15:03 UTC Jawid Talash <jawidtalash786@gmail.com>
` Re: current stable version for oracle linux 8 and 9
2026-09-09 15:18 UTC Peter Gram <peter.m.gram@gmail.com>
` Re: current stable version for oracle linux 8 and 9
2026-09-09 15:55 UTC Holger Jakobs <holger@jakobs.com>
[3+ messages in thread]
fetch all from "<unnamed portal 1>"
2026-09-09 04:31 UTC Siraj G <tosiraj.g@gmail.com>
` Re: fetch all from "<unnamed portal 1>"
2026-09-09 05:12 UTC Ganesh Korde <ganeshakorde@gmail.com>
` Re: fetch all from "<unnamed portal 1>"
2026-09-09 06:14 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: fetch all from "<unnamed portal 1>"
2026-09-09 11:45 UTC Siraj G <tosiraj.g@gmail.com>
` Re: fetch all from "<unnamed portal 1>"
2026-09-09 12:36 UTC Thomas Carroll <tomfecarroll@yahoo.com>
` Re: fetch all from "<unnamed portal 1>"
2026-09-09 12:56 UTC Shane Borden <shaneborden@google.com>
[6+ messages in thread]
Is there a way to avoid “refresh materialized view” generating WAL?
2026-09-08 01:50 UTC 李明 <liming185216@126.com>
` Re: Is there a way to avoid “refresh materialized view” generating WAL?
2026-09-08 05:05 UTC 李明 <liming185216@126.com>
` Re: Is there a way to avoid “refresh materialized view” generating WAL?
2026-09-08 05:49 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Is there a way to avoid “refresh materialized view” generating WAL?
2026-09-08 14:15 UTC Shaun Thomas <shaun.thomas@pgedge.com>
[4+ messages in thread]
what is the difference between ROLE clause and IN ROLE clause for CREATE USER statement ?
2026-09-02 05:15 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: what is the difference between ROLE clause and IN ROLE clause for CREATE USER statement ?
2026-09-02 05:52 UTC Benjamin Leis <benleis1@gmail.com>
` Re: what is the difference between ROLE clause and IN ROLE clause for CREATE USER statement ?
2026-09-02 05:55 UTC Kristjan Mustkivi <sonicmonkey@gmail.com>
` Re: what is the difference between ROLE clause and IN ROLE clause for CREATE USER statement ?
2026-09-02 07:34 UTC Alija Rahmanovic <rmc.aly17@gmail.com>
` Re: what is the difference between ROLE clause and IN ROLE clause for CREATE USER statement ?
2026-09-02 18:31 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
[5+ messages in thread]
Feature Request: pg_stat_activity.client_hostname and Unix sockets
2026-09-01 16:14 UTC Ron Johnson <ronljohnsonjr@gmail.com>
How to definitively determine whether a statement is a SELECT statement?
2026-08-31 16:06 UTC Ron Johnson <ronljohnsonjr@gmail.com>
` Re: How to definitively determine whether a statement is a SELECT statement?
2026-09-01 05:07 UTC bertrand HARTWIG <hartwig.bertrand@gmail.com>
[2+ messages in thread]
Unused Indexes
2026-08-18 12:58 UTC SASIKUMAR Devaraj <sashikumard@yahoo.com>
` Re: Unused Indexes
2026-08-18 13:10 UTC Ian Lawrence Barwick <barwick@gmail.com>
` Re: Unused Indexes
2026-08-18 17:44 UTC Thomas Carroll <tomfecarroll@yahoo.com>
` Re: Unused Indexes
2026-08-18 17:48 UTC Alex Shapalov <shapalov@gmail.com>
` Re: Unused Indexes
2026-08-18 18:05 UTC Gyanuba Gyanuba <gyanubagyanuba@gmail.com>
` Re: Unused Indexes
2026-08-24 15:07 UTC Gyanuba Gyanuba <gyanubagyanuba@gmail.com>
[6+ messages in thread]
PostgreSQL Replication Lag – WALs Streaming but Not Being Applied
2026-08-18 18:03 UTC Simon Musila - Localhost <smusila1@gmail.com>
` Re: PostgreSQL Replication Lag – WALs Streaming but Not Being Applied
2026-08-18 18:06 UTC Gyanuba Gyanuba <gyanubagyanuba@gmail.com>
` Re: PostgreSQL Replication Lag – WALs Streaming but Not Being Applied
2026-08-18 18:14 UTC Avinash Vallarapu <avinash.vallarapu@gmail.com>
` Re: PostgreSQL Replication Lag – WALs Streaming but Not Being Applied
2026-08-18 18:25 UTC Simon Musila - Localhost <smusila1@gmail.com>
` Re: PostgreSQL Replication Lag – WALs Streaming but Not Being Applied
2026-08-19 12:13 UTC hubert depesz lubaczewski <depesz@depesz.com>
[5+ messages in thread]
Urgent !!!! Tables inaccessible postgres v17.6
2026-08-06 14:11 UTC mahamood hussain <hussain.ieg@gmail.com>
` Re: Urgent !!!! Tables inaccessible postgres v17.6
2026-08-06 14:16 UTC Ron Johnson <ronljohnsonjr@gmail.com>
` Re: Urgent !!!! Tables inaccessible postgres v17.6
2026-08-06 14:27 UTC mahamood hussain <hussain.ieg@gmail.com>
` Re: Urgent !!!! Tables inaccessible postgres v17.6
2026-08-06 14:43 UTC Ron Johnson <ronljohnsonjr@gmail.com>
` Re: Urgent !!!! Tables inaccessible postgres v17.6
2026-08-06 14:57 UTC mahamood hussain <hussain.ieg@gmail.com>
` Re: Urgent !!!! Tables inaccessible postgres v17.6
2026-08-06 15:11 UTC Ron Johnson <ronljohnsonjr@gmail.com>
` Re: Urgent !!!! Tables inaccessible postgres v17.6
2026-08-06 15:40 UTC Pavan Deolasee <pavan.deolasee@gmail.com>
` Re: Urgent !!!! Tables inaccessible postgres v17.6
2026-08-06 15:42 UTC mahamood hussain <hussain.ieg@gmail.com>
` Re: Urgent !!!! Tables inaccessible postgres v17.6
2026-08-10 04:23 UTC mahamood hussain <hussain.ieg@gmail.com>
` Re: Urgent !!!! Tables inaccessible postgres v17.6
2026-08-10 12:39 UTC Licio Matos <licio.matos@gmail.com>
` Re: Urgent !!!! Tables inaccessible postgres v17.6
2026-08-13 08:55 UTC mahamood hussain <hussain.ieg@gmail.com>
` Re: Urgent !!!! Tables inaccessible postgres v17.6
2026-08-13 09:58 UTC Ireneusz Pluta <ipluta@wp.pl>
` Re: Urgent !!!! Tables inaccessible postgres v17.6
2026-08-13 12:19 UTC Licio Matos <licio.matos@gmail.com>
` Re: Urgent !!!! Tables inaccessible postgres v17.6
2026-08-14 09:10 UTC mahamood hussain <hussain.ieg@gmail.com>
` Re: Urgent !!!! Tables inaccessible postgres v17.6
2026-08-14 22:09 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[15+ messages in thread]
pg_upgrade from 17.10 to 18.4 on Ubuntu fails: Finding the real data directory for the target cluster sh: 1: (null)/postgres: not found
2026-08-12 10:50 UTC Holger Jakobs <holger@jakobs.com>
` Re: pg_upgrade from 17.10 to 18.4 on Ubuntu fails: Finding the real data directory for the target cluster sh: 1: (null)/postgres: not found
2026-08-12 15:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_upgrade from 17.10 to 18.4 on Ubuntu fails: Finding the real data directory for the target cluster sh: 1: (null)/postgres: not found
2026-08-13 12:37 UTC Michael Banck <mbanck@gmx.net>
[3+ messages in thread]
Pg_replay and pgshark
2026-08-10 11:49 UTC ek ek <livadidrive@gmail.com>
Re: PostgreSQL 14 standby recovery stuck in archive recovery state
2026-08-08 15:06 UTC Koen De Groote <kdg.dev@gmail.com>
MI - WAL issue
2026-07-27 05:57 UTC mahamood hussain <hussain.ieg@gmail.com>
` Re: MI - WAL issue
2026-07-27 08:06 UTC Jochen Bandhauer <jb@jbitc.de>
` Re: MI - WAL issue
2026-07-27 08:45 UTC Gaurav Shukla <gsricky391@gmail.com>
` Re: MI - WAL issue
2026-07-27 09:01 UTC mahamood hussain <hussain.ieg@gmail.com>
` Re: MI - WAL issue
2026-07-27 11:38 UTC sayli khedekar <saylikhedekar1@gmail.com>
[5+ messages in thread]
Subscription to community
2026-07-23 11:55 UTC Vani Majumdar <vani.majumdar@udulabs.com>
pgbackrest question
2026-07-22 20:13 UTC Murthy Nunna <mnunna@fnal.gov>
` Re: pgbackrest question
2026-07-22 20:21 UTC Ron Johnson <ronljohnsonjr@gmail.com>
` RE: pgbackrest question
2026-07-23 02:49 UTC Zechman, Derek S <Derek.S.Zechman@snapon.com>
` Re: pgbackrest question
2026-07-23 02:52 UTC Edu Joao <edujoao29@gmail.com>
` Re: pgbackrest question
2026-07-23 04:04 UTC Ron Johnson <ronljohnsonjr@gmail.com>
[5+ messages in thread]
Monitoring Streaming Replication
2026-07-20 13:34 UTC Daulat <daulat.dba@gmail.com>
` Re: Monitoring Streaming Replication
2026-07-20 14:32 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
test
2001-07-25 06:07 UTC Ang Sei Heng <seiheng@talariax.com>
` test
2002-12-09 09:40 UTC Ezra <epostgres@acedsl.com>
` test
2004-08-06 10:44 UTC Edgars <edzix19@inbox.lv>
` test
2004-12-07 00:26 UTC dedy <slackman@unika.ac.id>
` test
2006-03-16 15:02 UTC ute <ute@centrum.cz>
` test
2006-09-18 08:18 UTC Rafaqat Ali <smoken0@gmail.com>
` Re: test
2006-09-18 10:20 UTC Rafaqat Ali <smoken0@gmail.com>
` test
2007-08-14 18:06 UTC Medi Montaseri <montaseri@gmail.com>
` test
2020-02-24 10:12 UTC dbatoCloud Solution <dbatocloud17@gmail.com>
` test
2020-02-25 13:15 UTC dbatoCloud Solution <dbatocloud17@gmail.com>
` Re: test
2020-02-28 04:14 UTC Madeline Cummins <maddyc411@hotmail.com>
` test
2021-04-04 01:53 UTC Raul Garcia <rgarciaroves.mb@gmail.com>
` test
2026-07-07 03:09 UTC Hermawan Luly Muller <hermawanlulymuller@gmail.com>
` Re: test
2026-07-07 06:11 UTC Eduar Flow <eduarshorybalbuena77@gmail.com>
[14+ messages in thread]
PG version 16.14 upgrade went recovery state
2026-07-03 09:55 UTC K P Manoj <kpmanojpg@gmail.com>
` Re: PG version 16.14 upgrade went recovery state
2026-07-05 13:06 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: PG version 16.14 upgrade went recovery state
2026-07-06 16:02 UTC Michael Banck <mbanck@gmx.net>
` Re: PG version 16.14 upgrade went recovery state
2026-07-07 05:57 UTC K P Manoj <kpmanojpg@gmail.com>
[4+ messages in thread]
Any known bugs with respect to data corruption in pg12/pg 14
2026-06-03 12:14 UTC Ramakrishna Reddy Nandyala <rkreddy.n@gmail.com>
` Re: Any known bugs with respect to data corruption in pg12/pg 14
2026-06-03 12:32 UTC Alicja Kucharczyk <zaledwie10minut@gmail.com>
` Re: Any known bugs with respect to data corruption in pg12/pg 14
2026-07-07 04:29 UTC Alija Rahmanovic <rmc.aly17@gmail.com>
[3+ messages in thread]
Major upgrade in patroni cluster
2026-06-28 16:23 UTC Raj <rajeshkumar.dba09@gmail.com>
` Re: Major upgrade in patroni cluster
2026-07-06 10:36 UTC Mahesh Sathe <maheshsathe1@gmail.com>
` Re: Major upgrade in patroni cluster
2026-07-06 10:52 UTC Michael Banck <mbanck@gmx.net>
` Re: Major upgrade in patroni cluster
2026-07-06 10:56 UTC Michael Banck <mbanck@gmx.net>
[4+ messages in thread]
AW: Major upgrade in patroni cluster
2026-07-06 10:43 UTC Klaus Darilion <klaus.darilion@nic.at>
About asynchronous I/O
2026-06-23 07:55 UTC ek ek <livadidrive@gmail.com>
` Re: About asynchronous I/O
2026-06-23 11:25 UTC bertrand HARTWIG <hartwig.bertrand@gmail.com>
` Re: About asynchronous I/O
2026-06-23 12:02 UTC Ron Johnson <ronljohnsonjr@gmail.com>
` Re: About asynchronous I/O
2026-06-23 12:19 UTC bertrand HARTWIG <hartwig.bertrand@gmail.com>
` Re: About asynchronous I/O
2026-06-23 13:04 UTC JOHN WIENCEK <jwiencek3@comcast.net>
` Re: About asynchronous I/O
2026-06-23 13:35 UTC bertrand HARTWIG <hartwig.bertrand@gmail.com>
` Re: About asynchronous I/O
2026-06-23 13:58 UTC Scott Ribe <scott_ribe@elevated-dev.com>
` Re: About asynchronous I/O
2026-06-23 14:05 UTC Ron Johnson <ronljohnsonjr@gmail.com>
` Re: About asynchronous I/O
2026-06-23 14:19 UTC Michael Banck <mbanck@gmx.net>
[9+ messages in thread]
TPS in direct Postgres Vs TPS in pgbouncer
2026-06-21 13:24 UTC Raj <rajeshkumar.dba09@gmail.com>
` RE: TPS in direct Postgres Vs TPS in pgbouncer
2026-06-21 14:37 UTC Jorge Batista <Jorge.Batista@premier-research.com>
` Re: TPS in direct Postgres Vs TPS in pgbouncer
2026-06-21 19:19 UTC Jeffery Janes <jeff.janes@gmail.com>
[3+ messages in thread]
AW: Size of /pgdata
2026-06-17 13:59 UTC William Sescu (Suva) <william.sescu@suva.ch>
` AW: Size of /pgdata
2026-06-18 04:59 UTC William Sescu (Suva) <william.sescu@suva.ch>
` Re: AW: Size of /pgdata
2026-06-18 20:33 UTC Aleksey M Boltenkov <padrebolt@yandex.ru>
[3+ messages in thread]
[next (older)]
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox