pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedSource code package for libpq
2023-05-22 16:48 UTC Rajeshwar Singh <singh.rajeshwar@gmail.com>
` Re: Source code package for libpq
2023-05-22 17:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
trigger creation failed
2023-05-22 09:50 UTC Nikhil Ingale <niks.bgm@gmail.com>
` Re: trigger creation failed
2023-05-22 11:15 UTC kaido vaikla <kaido.vaikla@gmail.com>
[2+ messages in thread]
Vacuum Tuning Question
2023-05-19 15:35 UTC Murthy Nunna <mnunna@fnal.gov>
` Re: Vacuum Tuning Question
2023-05-19 15:48 UTC MichaelDBA <MichaelDBA@sqlexec.com>
` RE: Vacuum Tuning Question
2023-05-19 16:47 UTC Murthy Nunna <mnunna@fnal.gov>
` Re: Vacuum Tuning Question
2023-05-19 17:14 UTC Keith Fiske <keith.fiske@crunchydata.com>
` Re: Vacuum Tuning Question
2023-05-19 18:30 UTC Binh Le <binh.le.gso@gmail.com>
` Re: Vacuum Tuning Question
2023-05-19 20:36 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Vacuum Tuning Question
2023-05-20 00:50 UTC Jeff Janes <jeff.janes@gmail.com>
` RE: Vacuum Tuning Question
2023-05-20 15:49 UTC Murthy Nunna <mnunna@fnal.gov>
[8+ messages in thread]
Using pgadmin in docker via compose
2023-05-17 10:01 UTC Tim Uckun <timuckun@gmail.com>
` Re: Using pgadmin in docker via compose
2023-05-17 10:38 UTC Yogesh Mahajan <yogesh.mahajan@enterprisedb.com>
` Re: Using pgadmin in docker via compose
2023-05-20 10:07 UTC Tim Uckun <timuckun@gmail.com>
[3+ messages in thread]
ERROR: could not serialize access due to concurrent update
2023-05-16 12:38 UTC ROHIT SACHDEVA <sachdeva.rohit648@gmail.com>
` Re: ERROR: could not serialize access due to concurrent update
2023-05-16 13:09 UTC ROHIT SACHDEVA <sachdeva.rohit648@gmail.com>
` Re: ERROR: could not serialize access due to concurrent update
2023-05-16 13:44 UTC Ron <ronljohnsonjr@gmail.com>
` Re: ERROR: could not serialize access due to concurrent update
2023-05-16 15:33 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: ERROR: could not serialize access due to concurrent update
2023-05-16 16:21 UTC ROHIT SACHDEVA <sachdeva.rohit648@gmail.com>
` Re: ERROR: could not serialize access due to concurrent update
2023-05-16 16:35 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: ERROR: could not serialize access due to concurrent update
2023-05-16 17:24 UTC ROHIT SACHDEVA <sachdeva.rohit648@gmail.com>
` Re: ERROR: could not serialize access due to concurrent update
2023-05-16 18:08 UTC Scott Ribe <scott_ribe@elevated-dev.com>
` Re: ERROR: could not serialize access due to concurrent update
2023-05-17 06:10 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[9+ messages in thread]
Options for more aggressive space reclamation in vacuuming?
2023-05-14 17:45 UTC Wells Oliver <wells.oliver@gmail.com>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-14 18:32 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-14 21:02 UTC Wells Oliver <wells.oliver@gmail.com>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-14 22:08 UTC Paul Smith <paul@pscs.co.uk>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-14 22:19 UTC Wells Oliver <wells.oliver@gmail.com>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-14 22:25 UTC Ron <ronljohnsonjr@gmail.com>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-14 22:26 UTC Wells Oliver <wells.oliver@gmail.com>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-14 22:37 UTC Ron <ronljohnsonjr@gmail.com>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-14 22:43 UTC Ron <ronljohnsonjr@gmail.com>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-14 23:11 UTC Paul Smith <paul@pscs.co.uk>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-15 00:34 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-15 07:56 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-15 14:40 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-15 15:20 UTC Wolfgang Wilhelm <wolfgang20121964@yahoo.de>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-15 16:26 UTC Wells Oliver <wells.oliver@gmail.com>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-15 17:03 UTC Ron <ronljohnsonjr@gmail.com>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-15 17:05 UTC Wells Oliver <wells.oliver@gmail.com>
` Re: Options for more aggressive space reclamation in vacuuming?
2023-05-16 19:32 UTC Wolfgang Wilhelm <wolfgang20121964@yahoo.de>
[18+ messages in thread]
Getting error during execution of pg_dump
2023-05-16 08:57 UTC OS DB2 <opensourcedb2@gmail.com>
` Re: Getting error during execution of pg_dump
2023-05-16 15:34 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
Port 25060 failed: FATAL: pg_hba.conf rejects connection for host on Digital OCean
2023-05-16 13:48 UTC Uma Annamalai <uannamalai7@gmail.com>
` Re: Port 25060 failed: FATAL: pg_hba.conf rejects connection for host on Digital OCean
2023-05-16 15:22 UTC Wilson Coelho <wilson.coelho@tecnisys.com.br>
[2+ messages in thread]
Migrating MSSQL 2017 to Postgresql
2023-05-16 07:39 UTC Vishak Raj <vishak.shanmu@gmail.com>
` Re: Migrating MSSQL 2017 to Postgresql
2023-05-16 08:27 UTC Thomas Kellerer <shammat@gmx.net>
[2+ messages in thread]
Related To Vaccum Activity
2023-05-16 05:19 UTC ROHIT SACHDEVA <sachdeva.rohit648@gmail.com>
how do I capture conflicting rows
2023-05-15 05:32 UTC Nikhil Ingale <niks.bgm@gmail.com>
` Re: how do I capture conflicting rows
2023-05-15 06:09 UTC Ron <ronljohnsonjr@gmail.com>
` Re: how do I capture conflicting rows
2023-05-15 06:25 UTC Nikhil Ingale <niks.bgm@gmail.com>
` Re: how do I capture conflicting rows
2023-05-15 06:42 UTC Ron <ronljohnsonjr@gmail.com>
` Re: how do I capture conflicting rows
2023-05-15 11:15 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: how do I capture conflicting rows
2023-05-15 13:17 UTC Scott Ribe <scott_ribe@elevated-dev.com>
` Re: how do I capture conflicting rows
2023-05-15 13:58 UTC Mukesh Rajpurohit <vivasvan1902@gmail.com>
` Re: how do I capture conflicting rows
2023-05-15 14:53 UTC Rui DeSousa <rui@crazybean.net>
[8+ messages in thread]
Find out the indexed columns
2023-05-08 12:23 UTC Nikhil Ingale <niks.bgm@gmail.com>
` Re: Find out the indexed columns
2023-05-08 13:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Find out the indexed columns
2023-05-08 13:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Find out the indexed columns
2023-05-08 16:22 UTC Nikhil Ingale <niks.bgm@gmail.com>
` Re: Find out the indexed columns
2023-05-15 05:26 UTC Nikhil Ingale <niks.bgm@gmail.com>
[5+ messages in thread]
Unexplained rapid growth in memory usage of idle backends
2023-05-12 22:12 UTC Alex Balashov <abalashov@evaristesys.com>
` Re: Unexplained rapid growth in memory usage of idle backends
2023-05-12 23:38 UTC Erik Wienhold <ewie@ewie.name>
` Re: Unexplained rapid growth in memory usage of idle backends
2023-05-12 23:56 UTC Alex Balashov <abalashov@evaristesys.com>
` Re: Unexplained rapid growth in memory usage of idle backends
2023-05-13 01:17 UTC Erik Wienhold <ewie@ewie.name>
` Re: Unexplained rapid growth in memory usage of idle backends
2023-05-13 01:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Unexplained rapid growth in memory usage of idle backends
2023-05-13 15:09 UTC J T <jorge.torralba@gmail.com>
` Re: Unexplained rapid growth in memory usage of idle backends
2023-05-13 23:49 UTC Alex Balashov <abalashov@evaristesys.com>
` Re: Unexplained rapid growth in memory usage of idle backends
2023-05-13 23:57 UTC Alex Balashov <abalashov@evaristesys.com>
` Re: Unexplained rapid growth in memory usage of idle backends
2023-05-14 18:08 UTC Jeff Janes <jeff.janes@gmail.com>
[9+ messages in thread]
Frequency of pg_stat_all_tables updating?
2023-05-14 00:54 UTC Wells Oliver <wells.oliver@gmail.com>
` Re: Frequency of pg_stat_all_tables updating?
2023-05-14 01:09 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
pgsql code is not working.
2023-05-12 07:34 UTC Singh, Gambhir <gsingh2@kemper.com>
` Re: pgsql code is not working.
2023-05-13 01:33 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: pgsql code is not working.
2023-05-13 01:46 UTC David G. Johnston <david.g.johnston@gmail.com>
[3+ messages in thread]
ERROR: invalid message format and FATAL: invalid frontend message type XX logs
2023-05-12 08:57 UTC fatih abztn <fatihabztn@gmail.com>
` Re: ERROR: invalid message format and FATAL: invalid frontend message type XX logs
2023-05-12 12:27 UTC Dan Smith <j.daniel.smith1@gmail.com>
[2+ messages in thread]
ATTACH PARTITION "hangs"
2023-05-11 19:05 UTC kyle Hailey <kylelf@gmail.com>
` Re: ATTACH PARTITION "hangs"
2023-05-11 22:14 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: ATTACH PARTITION "hangs"
2023-05-11 22:44 UTC Keith <keith@keithf4.com>
` Re: ATTACH PARTITION "hangs"
2023-05-12 00:02 UTC kyle Hailey <kylelf@gmail.com>
[4+ messages in thread]
OS rpms needed to support install of postgres 15
2023-05-11 20:45 UTC chrisp@xmission.com
` Re: OS rpms needed to support install of postgres 15
2023-05-11 21:23 UTC Ron <ronljohnsonjr@gmail.com>
[2+ messages in thread]
Index recreation details with REINDEX TABLE CONCURRENTLY
2023-05-10 15:04 UTC Matthew Planchard <matthew@specprotected.com>
` Re: Index recreation details with REINDEX TABLE CONCURRENTLY
2023-05-10 20:36 UTC Ron <ronljohnsonjr@gmail.com>
` Re: Index recreation details with REINDEX TABLE CONCURRENTLY
2023-05-10 21:01 UTC James Fraley <jamesfraley@yahoo.com>
` Re: Index recreation details with REINDEX TABLE CONCURRENTLY
2023-05-11 16:09 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Index recreation details with REINDEX TABLE CONCURRENTLY
2023-05-11 16:19 UTC Katherine Mcmillan <kmcmi046@uottawa.ca>
` Re: Index recreation details with REINDEX TABLE CONCURRENTLY
2023-05-11 17:03 UTC Matthew Planchard <matthew@specprotected.com>
[6+ messages in thread]
nextval() on serial using old, existing value on insert?
2023-05-11 04:18 UTC Wells Oliver <wells.oliver@gmail.com>
` Re: nextval() on serial using old, existing value on insert?
2023-05-11 04:54 UTC Keith <keith@keithf4.com>
` Re: nextval() on serial using old, existing value on insert?
2023-05-11 04:55 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: nextval() on serial using old, existing value on insert?
2023-05-11 05:02 UTC Wells Oliver <wells.oliver@gmail.com>
` Re: nextval() on serial using old, existing value on insert?
2023-05-11 05:06 UTC Wells Oliver <wells.oliver@gmail.com>
` Re: nextval() on serial using old, existing value on insert?
2023-05-11 05:09 UTC Keith <keith@keithf4.com>
` Re: nextval() on serial using old, existing value on insert?
2023-05-11 05:10 UTC Wells Oliver <wells.oliver@gmail.com>
` Re: nextval() on serial using old, existing value on insert?
2023-05-11 12:38 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: nextval() on serial using old, existing value on insert?
2023-05-11 15:09 UTC Holger Jakobs <holger@jakobs.com>
` Re: nextval() on serial using old, existing value on insert?
2023-05-11 15:46 UTC Doug Reynolds <mav@wastegate.net>
[10+ messages in thread]
Related To Query Optimization
2023-05-11 14:50 UTC ROHIT SACHDEVA <sachdeva.rohit648@gmail.com>
` Re: Related To Query Optimization
2023-05-11 15:11 UTC Holger Jakobs <holger@jakobs.com>
[2+ messages in thread]
Question about pg_wal.tar.gz generated by pg_basebackup
2023-05-10 08:41 UTC Dhirendra Singh <dhirendraks@gmail.com>
` Re: Question about pg_wal.tar.gz generated by pg_basebackup
2023-05-10 12:06 UTC Stephen Frost <sfrost@snowman.net>
` Re: Question about pg_wal.tar.gz generated by pg_basebackup
2023-05-10 13:38 UTC Ron <ronljohnsonjr@gmail.com>
` Re: Question about pg_wal.tar.gz generated by pg_basebackup
2023-05-10 15:32 UTC Dhirendra Singh <dhirendraks@gmail.com>
[4+ messages in thread]
Patroni issue
2020-12-29 22:59 UTC Deepak tyagi <deepaktyagi454@gmail.com>
` Re: Patroni issue
2020-12-29 23:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Patroni Issue
2023-05-10 12:08 UTC Inzamam Shafiq <inzamam.shafiq@hotmail.com>
` Re: Patroni Issue
2023-05-10 12:13 UTC Stephen Frost <sfrost@snowman.net>
[4+ messages in thread]
The download page says that Pg 14 is available for RHEL 6
2023-05-09 14:24 UTC Ron <ronljohnsonjr@gmail.com>
unknown postgres ssl error "could not accept SSL connection: Success" and timeout
2023-05-03 13:55 UTC Sergey Cherevko <scherevko@scorewarrior.com>
` Re: unknown postgres ssl error "could not accept SSL connection: Success" and timeout
2023-05-04 08:16 UTC Holger Jakobs <holger@jakobs.com>
` Re: unknown postgres ssl error "could not accept SSL connection: Success" and timeout
2023-05-04 16:40 UTC Rui DeSousa <rui@crazybean.net>
` Re: unknown postgres ssl error "could not accept SSL connection: Success" and timeout
2023-05-04 16:49 UTC Rui DeSousa <rui@crazybean.net>
` Re: unknown postgres ssl error "could not accept SSL connection: Success" and timeout
2023-05-08 10:17 UTC Barjesh Vashist <barjeshvashist@gmail.com>
` Re: unknown postgres ssl error "could not accept SSL connection: Success" and timeout
2023-05-08 11:48 UTC Holger Jakobs <holger@jakobs.com>
[6+ messages in thread]
[next (older)]
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox