pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedReplication between two different versions
2023-03-07 15:42 UTC Erik Serrano <eserranos@gmail.com>
` Re: Replication between two different versions
2023-03-07 16:03 UTC Jwiencek3 <jwiencek3@comcast.net>
` Re: Replication between two different versions
2023-03-07 16:35 UTC J T <jorge.torralba@gmail.com>
` Re: Replication between two different versions
2023-03-07 16:44 UTC Erik Serrano <eserranos@gmail.com>
` Re: Replication between two different versions
2023-03-07 16:49 UTC J T <jorge.torralba@gmail.com>
` Re: Replication between two different versions
2023-03-08 00:56 UTC Abhishek Singh <abhi.singh.solanki@gmail.com>
[6+ messages in thread]
Migrating tables to new schema with minimal downtime
2023-03-06 21:00 UTC Joseph Hammerman <joe.hammerman@datadoghq.com>
` Re: Migrating tables to new schema with minimal downtime
2023-03-07 06:29 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Migrating tables to new schema with minimal downtime
2023-03-07 11:59 UTC hubert depesz lubaczewski <depesz@depesz.com>
[3+ messages in thread]
replication origin advance in pglogical extension
2023-03-03 07:37 UTC srinivas oguri <srinivasoguri7@gmail.com>
New PG14 server won't start with >2GB shared_buffers
2023-02-25 02:08 UTC Chris Hoover <chrish@aweber.com>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 02:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 03:29 UTC Chris Hoover <chrish@aweber.com>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 10:25 UTC Ron <ronljohnsonjr@gmail.com>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 10:33 UTC JP Pozzi <jpp@jppozzi.dyndns.org>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 13:07 UTC Chris Hoover <chrish@aweber.com>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 14:05 UTC MichaelDBA <MichaelDBA@sqlexec.com>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 14:49 UTC Kenneth Marshall <ktm@rice.edu>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 14:51 UTC Chris Hoover <chrish@aweber.com>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 14:51 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 14:53 UTC MichaelDBA <MichaelDBA@sqlexec.com>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 14:55 UTC Chris Hoover <chrish@aweber.com>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 14:57 UTC Chris Hoover <chrish@aweber.com>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 15:16 UTC Evan Rempel <erempel@uvic.ca>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 16:35 UTC Carlos Martinez <camarti@gmail.com>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 16:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 17:55 UTC Tim <timfosho@gmail.com>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-25 18:38 UTC Charles Bowers <charles.bowers@gmail.com>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-26 22:01 UTC Chris Hoover <chrish@aweber.com>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-27 00:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-02-27 16:25 UTC Chris Hoover <chrish@aweber.com>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-03-02 21:53 UTC Chris Hoover <chrish@aweber.com>
` Re: New PG14 server won't start with >2GB shared_buffers
2023-03-02 21:56 UTC MichaelDBA <MichaelDBA@sqlexec.com>
[23+ messages in thread]
Forcasting in Postgresql
2023-03-01 07:48 UTC Govardhan .G <govardhansrr@gmail.com>
` Re: Forcasting in Postgresql
2023-03-01 16:57 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Forcasting in Postgresql
2023-03-02 16:25 UTC Govardhan .G <govardhansrr@gmail.com>
` RE: Forcasting in Postgresql
2023-03-02 17:47 UTC dave@davebolt.co.uk
` Re: Forcasting in Postgresql
2023-03-02 17:51 UTC Govardhan .G <govardhansrr@gmail.com>
[5+ messages in thread]
psql terminates on first error
2023-03-02 11:53 UTC Holger Jakobs <holger@jakobs.com>
` Re: psql terminates on first error
2023-03-02 12:32 UTC Erik Wienhold <ewie@ewie.name>
` Re: psql terminates on first error
2023-03-02 12:44 UTC Holger Jakobs <holger@jakobs.com>
` Re: psql terminates on first error
2023-03-02 12:48 UTC Thomas Kellerer <shammat@gmx.net>
` Re: psql terminates on first error
2023-03-02 13:30 UTC Holger Jakobs <holger@jakobs.com>
` Re: psql terminates on first error
2023-03-02 13:45 UTC Erik Wienhold <ewie@ewie.name>
` Re: psql terminates on first error
2023-03-02 14:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: psql terminates on first error
2023-03-02 14:36 UTC Holger Jakobs <holger@jakobs.com>
[8+ messages in thread]
Create replication read only
2023-03-01 18:27 UTC Erik Serrano <eserranos@gmail.com>
` Re: Create replication read only
2023-03-01 22:00 UTC Ron <ronljohnsonjr@gmail.com>
[2+ messages in thread]
Query taking long with levenshtein function
2023-02-28 23:11 UTC Teju Jakkidi vlogs <teja.jakkidi05@gmail.com>
` Re: Query taking long with levenshtein function
2023-02-28 23:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query taking long with levenshtein function
2023-03-01 00:22 UTC Edward J. Sabol <edwardjsabol@gmail.com>
` Re: Query taking long with levenshtein function
2023-03-01 06:57 UTC Edward J. Sabol <edwardjsabol@gmail.com>
[4+ messages in thread]
pg_dump: error: could not open large object
2023-02-24 14:55 UTC Ankur Kaushik <ankurkaushik@gmail.com>
` Re: pg_dump: error: could not open large object
2023-02-24 14:58 UTC Ankur Kaushik <ankurkaushik@gmail.com>
` Re: pg_dump: error: could not open large object
2023-02-24 15:07 UTC Ron <ronljohnsonjr@gmail.com>
[3+ messages in thread]
PostgreSQL, change encoding preserving data
2023-02-23 13:00 UTC info@denisgottardello.it
` Re: PostgreSQL, change encoding preserving data
2023-02-23 13:18 UTC Holger Jakobs <holger@jakobs.com>
` Re: PostgreSQL, change encoding preserving data
2023-02-23 13:52 UTC Norbert Poellmann <np@ibu.de>
` Re: PostgreSQL, change encoding preserving data
2023-02-24 13:00 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[4+ messages in thread]
AutoExplain printing sql_hash and plan_hash
2023-02-24 04:45 UTC ashok raj <ashokexplorer@gmail.com>
` Re: AutoExplain printing sql_hash and plan_hash
2023-02-24 05:04 UTC Julien Rouhaud <rjuju123@gmail.com>
[2+ messages in thread]
Alter default privileges is not working for roles
2023-02-22 17:52 UTC Teju Jakkidi vlogs <teja.jakkidi05@gmail.com>
` Re: Alter default privileges is not working for roles
2023-02-22 18:32 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Alter default privileges is not working for roles
2023-02-22 21:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
pg_dump error
2000-04-17 03:02 UTC Joe Conway <jconway2@home.com>
` pg_dump ERROR .......
2001-03-28 12:07 UTC agichen@kimo.com
` pg_dump error
2002-02-25 21:32 UTC Srinivasa Rao Chava <s.chava@wcom.com>
` Re: pg_dump error
2002-02-25 22:42 UTC Stephan Szabo <sszabo@megazone23.bigpanda.com>
` Re: pg_dump error
2002-02-25 23:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` pg_dump error
2002-10-01 15:52 UTC Ferdinand Smit <ferdinand@telegraafnet.nl>
` Re: pg_dump error
2002-10-01 17:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
` pg_dump error
2003-11-06 17:35 UTC David C. Brown <dbrown@centennialwines.com>
` Re: pg_dump error
2003-11-06 18:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump error
2003-11-06 18:23 UTC David C. Brown <dbrown@centennialwines.com>
` pg_dump Error
2004-06-29 09:38 UTC Nigel Bishop <Nigel.Bishop@ioko.com>
` Re: pg_dump Error
2004-06-29 11:27 UTC Guido Barosio <gbarosio@sinectis.com.ar>
` Re: pg_dump Error
2004-06-29 14:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` pg_dump error
2005-09-07 09:50 UTC Adam Witney <awitney@sgul.ac.uk>
` Re: pg_dump error
2005-09-07 14:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump error
2005-09-07 14:55 UTC Michael Fuhr <mike@fuhr.org>
` Re: pg_dump error
2005-09-07 15:08 UTC Adam Witney <awitney@sgul.ac.uk>
` Re: pg_dump error
2005-09-07 15:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump error
2005-09-07 15:40 UTC Adam Witney <awitney@sgul.ac.uk>
` Re: pg_dump error
2005-09-07 15:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` pg_dump error
2005-09-28 15:13 UTC Jerry Cadet <jjrc71@hotmail.com>
` PG_DUMP Error
2005-10-06 10:33 UTC Cédric Buschini <cbuschini@carax.com>
` pg_dump error
2006-07-06 12:25 UTC manjula hettiarachchi <manjula_55@yahoo.com>
` Re: pg_dump error
2006-07-06 12:29 UTC Dilipkumar <dilipkumar_parikh@sifycorp.com>
` FWD: [ADMIN] pg_dump error
2006-07-06 12:52 UTC Guido Barosio <gbarosio@gmail.com>
` Fwd: Re: pg_dump error
2006-07-07 04:17 UTC manjula hettiarachchi <manjula_55@yahoo.com>
` Re: FWD: [ADMIN] pg_dump error
2006-07-07 04:38 UTC Christopher Browne <cbbrowne@acm.org>
` Re: FWD: [ADMIN] pg_dump error
2006-07-07 11:20 UTC Robert Treat <xzilla@users.sourceforge.net>
` pg_dump error
2007-02-28 19:17 UTC Karthikeyan Sundaram <skarthi98@hotmail.com>
` Re: pg_dump error
2007-02-28 19:31 UTC Joshua D. Drake <jd@commandprompt.com>
` Re: pg_dump error
2007-02-28 19:35 UTC Karthikeyan Sundaram <skarthi98@hotmail.com>
` Re: [SQL] pg_dump error
2007-03-02 06:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` pg_dump error
2015-07-20 10:51 UTC Campbell, Lance <lance@illinois.edu>
` Re: pg_dump error
2015-07-20 11:23 UTC Campbell, Lance <lance@illinois.edu>
` Re: pg_dump error
2015-07-20 12:31 UTC Campbell, Lance <lance@illinois.edu>
` Re: pg_dump error
2015-07-20 13:03 UTC Campbell, Lance <lance@illinois.edu>
` Re: pg_dump error
2015-07-20 13:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` pg_dump: error
2023-02-22 16:17 UTC Alessandro Papa - Infolab <a.papa@infolabonline.com>
` Re: pg_dump: error
2023-02-22 16:44 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: pg_dump: error
2023-02-22 17:15 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[40+ messages in thread]
Select statement error in PostgreSQL 11.9
2023-02-21 19:24 UTC Mohammed Afsar <vmdapsar@gmail.com>
` Re: Select statement error in PostgreSQL 11.9
2023-02-21 20:34 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
Is it possible to log long running recursive/internal postgresql queries?
2023-02-17 17:48 UTC Hotmail <crajac66@hotmail.com>
` Re: Is it possible to log long running recursive/internal postgresql queries?
2023-02-17 18:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Is it possible to log long running recursive/internal postgresql queries?
2023-02-20 13:52 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Is it possible to log long running recursive/internal postgresql queries?
2023-02-20 15:53 UTC Hotmail <crajac66@hotmail.com>
` Re: Is it possible to log long running recursive/internal postgresql queries?
2023-02-21 09:48 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[5+ messages in thread]
Vacuum and analyze for objects on physical stand by dbs
2023-02-18 01:31 UTC Teja Jakkidi <teja.jakkidi05@gmail.com>
` Re: Vacuum and analyze for objects on physical stand by dbs
2023-02-18 02:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Vacuum and analyze for objects on physical stand by dbs
2023-02-18 15:09 UTC obi reddy <obireddy.g1997@gmail.com>
` Re: Vacuum and analyze for objects on physical stand by dbs
2023-02-20 21:22 UTC Teja Jakkidi <teja.jakkidi05@gmail.com>
[4+ messages in thread]
EOL of Pglogical replication support
2023-02-16 19:56 UTC pradeep pandey <pandeyp@hotmail.com>
` Re: EOL of Pglogical replication support
2023-02-17 17:19 UTC pradeep pandey <pandeyp@hotmail.com>
` Re: EOL of Pglogical replication support
2023-02-17 21:00 UTC Lucio Chiessi <lucio.chiessi@trustly.com>
` Re: EOL of Pglogical replication support
2023-02-17 21:12 UTC pradeep pandey <pandeyp@hotmail.com>
[4+ messages in thread]
Redirect RAISE NOTICE and errors to separate log file
2023-02-17 15:59 UTC Nikhil Ingale <niks.bgm@gmail.com>
` Re: Redirect RAISE NOTICE and errors to separate log file
2023-02-17 16:27 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Redirect RAISE NOTICE and errors to separate log file
2023-02-17 16:51 UTC Nikhil Ingale <niks.bgm@gmail.com>
` Re: Redirect RAISE NOTICE and errors to separate log file
2023-02-17 16:58 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Redirect RAISE NOTICE and errors to separate log file
2023-02-17 17:20 UTC Nikhil Ingale <niks.bgm@gmail.com>
[5+ messages in thread]
Upgrading postgres quickly, without downtime.
2023-02-17 09:31 UTC Karthik Krishnakumar <karthikk@zohocorp.com>
` Re: Upgrading postgres quickly, without downtime.
2023-02-17 12:13 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Upgrading postgres quickly, without downtime.
2023-02-17 13:00 UTC MichaelDBA <MichaelDBA@sqlexec.com>
[3+ messages in thread]
Load 500 GB test data with Large objects and different types
2023-02-16 18:45 UTC Raj kumar <rajkumar820999@gmail.com>
` Re: Load 500 GB test data with Large objects and different types
2023-02-16 20:02 UTC Lucio Chiessi <lucio.chiessi@trustly.com>
` Re: Load 500 GB test data with Large objects and different types
2023-02-16 21:03 UTC Holger Jakobs <holger@jakobs.com>
[3+ messages in thread]
pglogical performance for copying large table
2023-02-13 18:29 UTC srinivas oguri <srinivasoguri7@gmail.com>
` Re: pglogical performance for copying large table
2023-02-13 20:41 UTC Carrie Berlin <berlincarrie@gmail.com>
` Re: pglogical performance for copying large table
2023-02-13 22:37 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: pglogical performance for copying large table
2023-02-14 02:08 UTC srinivas oguri <srinivasoguri7@gmail.com>
[4+ messages in thread]
API call in SPROC
2023-02-13 09:44 UTC Anjul Tyagi <anjul@ibosstech-us.com>
` Re: API call in SPROC
2023-02-13 17:46 UTC Wells Oliver <wells.oliver@gmail.com>
[2+ messages in thread]
Upgrade from PostGIS 2.3 to 2.5.5 in PostgreSQL 11 error
2023-02-12 20:56 UTC ghadeerdarwesh58@gmail.com
` Re: Upgrade from PostGIS 2.3 to 2.5.5 in PostgreSQL 11 error
2023-02-13 01:15 UTC Erik Wienhold <ewie@ewie.name>
[2+ messages in thread]
Re: UPDATE, pglogical supervisor on pg15 not taking ProcSignalBarrier
2023-02-10 20:32 UTC Jerry Sievers <gsievers19@comcast.net>
pglogical supervisor on pg15 not taking ProcSignalBarrier
2023-02-10 17:47 UTC Jerry Sievers <gsievers19@comcast.net>
[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