agora inbox for pgsql-admin@postgresql.org
help / color / mirror / Atom feedpg_dump
42+ messages / 23 participants
[nested] [flat]
* pg_dump
@ 2000-08-04 08:43 julien piaser <jpiaser@lxsolutions.com>
0 siblings, 0 replies; 42+ messages in thread
From: julien piaser @ 2000-08-04 08:43 UTC (permalink / raw)
To: pgsql-admin
when enabling the password identification, how can I manage to write a
script to backup my database so it can automaticly be executed... The
problem comes from pg_dump (or pg_dumpall) that both prompt for my login
and password, and I can't give it as an one line argument...
Any suggestions?
regards
J.Piaser
^ permalink raw reply [nested|flat] 42+ messages in thread
* pg_dump
@ 2002-07-19 20:53 Robson Martins <robson-martins@bol.com.br>
0 siblings, 0 replies; 42+ messages in thread
From: Robson Martins @ 2002-07-19 20:53 UTC (permalink / raw)
To: pgsql-admin
Sou super usuário (postgres), no entando não consigo efetuar o pg_dump em meu banco. a mensagem que aparece é esta:
pg_dump -c televendas | gzip > tmkt.db.gz
WARNING: owner of type 'capitais' appears to be invalid
WARNING: owner of type 'cepespeciais' appears to be
alguêm poderia ajudar???
Robson
^ permalink raw reply [nested|flat] 42+ messages in thread
* PG_DUMP
@ 2003-12-31 08:01 omkar prabhu <oprabhu@phildigital.com>
0 siblings, 0 replies; 42+ messages in thread
From: omkar prabhu @ 2003-12-31 08:01 UTC (permalink / raw)
To: pgsql-admin
Hi,
I am trying to dump large object data( from a database containing table consist of 4 lo fields)
I get following error.
I am using postgres 7.2.1 which is installed from rpm
Command use is
pg_dump -Ft -b test1 > db.tar
I get following message
pg_dump: WARNING: function "lo_oid" not dumped
pg_dump: reason: data type name of argument 0 (oid 16584) not found
When i try restore using pg_restore
Blob data is restored.
Same i tried to postgres7.2.1 which is compiled and install it works fine.
What could be the problem?
Is there anyway by which i can fixed this problem by using postgres which is installed using rpm
^ permalink raw reply [nested|flat] 42+ messages in thread
* Pg_dump
@ 2004-12-26 10:09 Gourish Singbal <gourish@gmail.com>
0 siblings, 1 reply; 42+ messages in thread
From: Gourish Singbal @ 2004-12-26 10:09 UTC (permalink / raw)
To: pgsql-admin
1) I want to take a pg_dump of only few tables
/usr/local/pgsql/bin/pg_dump -t [table_name] database_name > file.out
allows me only to take dump of single table. Is there a way to take
dump of more than one specific tables.
2) Does pg_dump allow me to take dump of a table so that only some
records are included in the dump (Some thing like specifying a QUERY
in the pg_dump)
--
Best,
Gourish Singbal
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2004-12-26 17:47 Bruno Wolff III <bruno@wolff.to>
parent: Gourish Singbal <gourish@gmail.com>
0 siblings, 1 reply; 42+ messages in thread
From: Bruno Wolff III @ 2004-12-26 17:47 UTC (permalink / raw)
To: Gourish Singbal <gourish@gmail.com>; +Cc: pgsql-admin
On Sun, Dec 26, 2004 at 15:39:48 +0530,
Gourish Singbal <gourish@gmail.com> wrote:
> 1) I want to take a pg_dump of only few tables
>
> /usr/local/pgsql/bin/pg_dump -t [table_name] database_name > file.out
>
> allows me only to take dump of single table. Is there a way to take
> dump of more than one specific tables.
I think this is a new feature for 8.0.
> 2) Does pg_dump allow me to take dump of a table so that only some
> records are included in the dump (Some thing like specifying a QUERY
> in the pg_dump)
I suspect the best way to do this is to create a new table, select the desired
records into that table and then dump it.
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2004-12-26 23:33 Tom Lane <tgl@sss.pgh.pa.us>
parent: Bruno Wolff III <bruno@wolff.to>
0 siblings, 1 reply; 42+ messages in thread
From: Tom Lane @ 2004-12-26 23:33 UTC (permalink / raw)
To: Bruno Wolff III <bruno@wolff.to>; +Cc: Gourish Singbal <gourish@gmail.com>; pgsql-admin
Bruno Wolff III <bruno@wolff.to> writes:
> Gourish Singbal <gourish@gmail.com> wrote:
>> allows me only to take dump of single table. Is there a way to take
>> dump of more than one specific tables.
> I think this is a new feature for 8.0.
No, it's not in 8.0 either; you still need a separate pg_dump run for each
table.
regards, tom lane
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2004-12-27 14:27 Spiegelberg, Greg <gspiegelberg@cranel.com>
0 siblings, 1 reply; 42+ messages in thread
From: Spiegelberg, Greg @ 2004-12-27 14:27 UTC (permalink / raw)
To: pgsql-admin
Benig able to exclude tables from dump's would be useful as well.
Greg
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Sunday, December 26, 2004 6:34 PM
To: Bruno Wolff III
Cc: Gourish Singbal; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Pg_dump
Bruno Wolff III <bruno@wolff.to> writes:
> Gourish Singbal <gourish@gmail.com> wrote:
>> allows me only to take dump of single table. Is there a way to take
>> dump of more than one specific tables.
> I think this is a new feature for 8.0.
No, it's not in 8.0 either; you still need a separate pg_dump run for each
table.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2004-12-27 21:01 Bruno Wolff III <bruno@wolff.to>
parent: Spiegelberg, Greg <gspiegelberg@cranel.com>
0 siblings, 0 replies; 42+ messages in thread
From: Bruno Wolff III @ 2004-12-27 21:01 UTC (permalink / raw)
To: Spiegelberg, Greg <gspiegelberg@cranel.com>; +Cc: pgsql-admin
On Mon, Dec 27, 2004 at 09:27:53 -0500,
"Spiegelberg, Greg" <gspiegelberg@cranel.com> wrote:
> Benig able to exclude tables from dump's would be useful as well.
There was some discussion about doing this kind of thing about 6 months
ago (shortly before beta). I appearantly misremembered the end result
of the discussion, but you should be able to find it in the archives.
>
> Greg
>
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Sunday, December 26, 2004 6:34 PM
> To: Bruno Wolff III
> Cc: Gourish Singbal; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Pg_dump
>
>
> Bruno Wolff III <bruno@wolff.to> writes:
> > Gourish Singbal <gourish@gmail.com> wrote:
> >> allows me only to take dump of single table. Is there a way to take
> >> dump of more than one specific tables.
>
> > I think this is a new feature for 8.0.
>
> No, it's not in 8.0 either; you still need a separate pg_dump run for each
> table.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2004-12-28 15:55 Gourish Singbal <gourish@gmail.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 42+ messages in thread
From: Gourish Singbal @ 2004-12-28 15:55 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Bruno Wolff III <bruno@wolff.to>; pgsql-admin
Thanks
i will try to find the answer in the archives,
Also will having a saperate schema for a set of tables help me in
taking pg_dump only of specific tables. is it possible to create
schema for already existing postgresql database tables ?.
Also how do i know is any tables need recovery...
like in oracle we come to know from a view called as v$recovery_log.
is some thing like is this possible in postgres.
Best
Gourish
On Sun, 26 Dec 2004 18:33:37 -0500, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Bruno Wolff III <bruno@wolff.to> writes:
> > Gourish Singbal <gourish@gmail.com> wrote:
> >> allows me only to take dump of single table. Is there a way to take
> >> dump of more than one specific tables.
>
> > I think this is a new feature for 8.0.
>
> No, it's not in 8.0 either; you still need a separate pg_dump run for each
> table.
>
> regards, tom lane
>
--
Best,
Gourish Singbal
^ permalink raw reply [nested|flat] 42+ messages in thread
* pg_dump
@ 2005-10-10 05:30 Nirav Parikh <nirav.p@workskillsprofessionals.com.au>
0 siblings, 1 reply; 42+ messages in thread
From: Nirav Parikh @ 2005-10-10 05:30 UTC (permalink / raw)
To: pgsql-admin
Hi,
I am trying to write cronjob so it will backup database everynight on
another machine.
Currently is doing it on the same machine with this script.
20 13 * * * pg_dump -F c -f /root/database.pgdump database
How can I send it to different machine. Machine IP address is
192.168.1.13
Is it possible to write pg_restore job ones it finishes dumping on that
machine?
Does anybody know how to do this?
Thanks in Advance.
Regards,
Neo
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: pg_dump
@ 2005-10-10 06:48 Luca Ferrari <fluca1978@infinito.it>
parent: Nirav Parikh <nirav.p@workskillsprofessionals.com.au>
0 siblings, 0 replies; 42+ messages in thread
From: Luca Ferrari @ 2005-10-10 06:48 UTC (permalink / raw)
To: pgsql-admin
Nirav Parikh's cat, on 10/10/2005 7.30, walking on the keyboard wrote:
> Hi,
>
> I am trying to write cronjob so it will backup database everynight on
> another machine.
> Currently is doing it on the same machine with this script.
>
> 20 13 * * * pg_dump -F c -f /root/database.pgdump database
>
> How can I send it to different machine. Machine IP address is
> 192.168.1.13
You can use ssh to copy the dump file to another machine. Configuring
ssh to use ssh_agent you will not be required to insert a passwrod, thus
you can do it automatically. I guess there's also an option to specify
the password on the command line.
>
> Is it possible to write pg_restore job ones it finishes dumping on that
> machine?
I guess you can write a shell script that checks, periodically, if the
restore file has been copied, then restores it and delete the files
(thus to not restore it infinitely).
Luca
--
Luca Ferrari
fluca1978@infinito.it
^ permalink raw reply [nested|flat] 42+ messages in thread
* PG_DUMP
@ 2006-05-26 04:50 renneyt@yahoo.com <renneyt@yahoo.com>
0 siblings, 1 reply; 42+ messages in thread
From: renneyt@yahoo.com @ 2006-05-26 04:50 UTC (permalink / raw)
To: pgsql-admin
Is there a way to do a selective pg_dump of a table using a select where
clause? As in ... dump all records where now-col_date < 2 or
col_date='01-may-2006' etc.. ?
Thanks
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: PG_DUMP
@ 2006-05-26 13:45 Jeff Boes <jeff@endpoint.com>
parent: renneyt@yahoo.com <renneyt@yahoo.com>
0 siblings, 0 replies; 42+ messages in thread
From: Jeff Boes @ 2006-05-26 13:45 UTC (permalink / raw)
To: pgsql-admin; +Cc: renneyt@yahoo.com <renneyt@yahoo.com>
renneyt@yahoo.com wrote:
> Is there a way to do a selective pg_dump of a table using a select
> where clause? As in ... dump all records where now-col_date < 2 or
> col_date='01-may-2006' etc.. ?
You can transfer the subset of data to another table, e.g.,
create table my_dump as select * from table_foo where ...
and then dump that table. Note that you can't do this to a view (pg_dump
will dump the view definition, but not the data).
--
Jeffery Boes <><
jeff@endpoint.com
^ permalink raw reply [nested|flat] 42+ messages in thread
* pg_dump
@ 2015-12-23 22:27 Artem Tomyuk <admin@leboutique.com>
0 siblings, 1 reply; 42+ messages in thread
From: Artem Tomyuk @ 2015-12-23 22:27 UTC (permalink / raw)
To: pgsql-admin
Hi.
Why in pg_dump there is no feature --jobs=number-of-jobs
like in pg_restore?
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: pg_dump
@ 2015-12-23 22:29 Artem Tomyuk <admin@leboutique.com>
parent: Artem Tomyuk <admin@leboutique.com>
0 siblings, 0 replies; 42+ messages in thread
From: Artem Tomyuk @ 2015-12-23 22:29 UTC (permalink / raw)
To: pgsql-admin
Sorry, my bad.
2015-12-24 0:27 GMT+02:00 Artem Tomyuk <admin@leboutique.com>:
> Hi.
>
> Why in pg_dump there is no feature --jobs=number-of-jobs
> like in pg_restore?
>
^ permalink raw reply [nested|flat] 42+ messages in thread
* Pg_dump
@ 2021-12-07 07:08 Firthouse banu <penguinsfairy@gmail.com>
0 siblings, 2 replies; 42+ messages in thread
From: Firthouse banu @ 2021-12-07 07:08 UTC (permalink / raw)
To: pgsql-admin
Pg_dump missing -d option … It was working fine till yesterday suddenly
today I see this option is missing in one of our server. Any
suggestions????
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2021-12-07 12:55 David G. Johnston <david.g.johnston@gmail.com>
parent: Firthouse banu <penguinsfairy@gmail.com>
1 sibling, 0 replies; 42+ messages in thread
From: David G. Johnston @ 2021-12-07 12:55 UTC (permalink / raw)
To: Firthouse banu <penguinsfairy@gmail.com>; +Cc: pgsql-admin
On Tuesday, December 7, 2021, Firthouse banu <penguinsfairy@gmail.com>
wrote:
> Pg_dump missing -d option … It was working fine till yesterday suddenly
> today I see this option is missing in one of our server. Any
> suggestions????
It seems more likely you are misunderstanding whatever unstated error
message you are seeing…
David J.
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2021-12-07 14:18 Mladen Gogala <gogala.mladen@gmail.com>
parent: Firthouse banu <penguinsfairy@gmail.com>
1 sibling, 1 reply; 42+ messages in thread
From: Mladen Gogala @ 2021-12-07 14:18 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
On 12/7/21 02:08, Firthouse banu wrote:
> Pg_dump missing -d option … It was working fine till yesterday
> suddenly today I see this option is missing in one of our server. Any
> suggestions????
Maybe the option took a vacation on Barbados? Have you checked your
email for auto-response? Barbados is beautiful this time of year. If you
need more serious response, you will have to provide more data:
1. What version of PostgreSQL are you using?
2. What has changed since yesterday?
3. Have you checked logs?
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2021-12-07 15:06 Scott Ribe <scott_ribe@elevated-dev.com>
parent: Mladen Gogala <gogala.mladen@gmail.com>
0 siblings, 0 replies; 42+ messages in thread
From: Scott Ribe @ 2021-12-07 15:06 UTC (permalink / raw)
To: Mladen Gogala <gogala.mladen@gmail.com>; +Cc: pgsql-admin@lists.postgresql.org
Most likely: you have omitted a previous argument which results in -d being taken as an arg instead of a flag
^ permalink raw reply [nested|flat] 42+ messages in thread
* Pg_dump
@ 2023-12-07 18:11 Rajesh Kumar <rajeshkumar.dba09@gmail.com>
0 siblings, 1 reply; 42+ messages in thread
From: Rajesh Kumar @ 2023-12-07 18:11 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Hi
Will pg_dump cause blocking queries? If so how to take dump without
blocking?
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2023-12-07 18:13 Holger Jakobs <holger@jakobs.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
0 siblings, 2 replies; 42+ messages in thread
From: Holger Jakobs @ 2023-12-07 18:13 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org; +Cc: rajeshkumar.dba09@gmail.com
Am 07.12.23 um 19:11 schrieb Rajesh Kumar:
> Hi
>
> Will pg_dump cause blocking queries? If so how to take dump without
> blocking?
Readers don't block writers, writers don't block readers in PostgreSQL.
pg_dump is a reader.
--
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
Attachments:
[application/pgp-signature] OpenPGP_signature (202B, ../../404a126a-6229-7d83-9b86-70304a5693bc@jakobs.com/2-OpenPGP_signature)
download
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2023-12-07 18:26 Scott Ribe <scott_ribe@elevated-dev.com>
parent: Holger Jakobs <holger@jakobs.com>
1 sibling, 1 reply; 42+ messages in thread
From: Scott Ribe @ 2023-12-07 18:26 UTC (permalink / raw)
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
> Readers don't block writers, writers don't block readers in PostgreSQL.
>
> pg_dump is a reader.
>
> --
> Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
Additionally, I've done some stress testing and found that pg_dump puts surprisingly low load on our dbs. Of course, like everything else, this dependent on your specifics--after all the dump will require reading all rows, so for instance if you're disk-bound, you could see a performance hit. But generally, if your db is running in a reasonably "healthy" performance range and not already close to limits, pg_dump won't have a performance impact visible to users.
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2023-12-07 18:39 jason cable <cablej2082@gmail.com>
parent: Scott Ribe <scott_ribe@elevated-dev.com>
0 siblings, 0 replies; 42+ messages in thread
From: jason cable @ 2023-12-07 18:39 UTC (permalink / raw)
To: Scott Ribe <scott_ribe@elevated-dev.com>; Rajesh Kumar <rajeshkumar.dba09@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
That happens to me too the last time I took dump
Get Outlook for Android<https://aka.ms/AAb9ysg;
________________________________
From: Scott Ribe <scott_ribe@elevated-dev.com>
Sent: Thursday, December 7, 2023 10:26:15 AM
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Pg_dump
> Readers don't block writers, writers don't block readers in PostgreSQL.
>
> pg_dump is a reader.
>
> --
> Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
Additionally, I've done some stress testing and found that pg_dump puts surprisingly low load on our dbs. Of course, like everything else, this dependent on your specifics--after all the dump will require reading all rows, so for instance if you're disk-bound, you could see a performance hit. But generally, if your db is running in a reasonably "healthy" performance range and not already close to limits, pg_dump won't have a performance impact visible to users.
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2023-12-07 18:52 Tom Lane <tgl@sss.pgh.pa.us>
parent: Holger Jakobs <holger@jakobs.com>
1 sibling, 1 reply; 42+ messages in thread
From: Tom Lane @ 2023-12-07 18:52 UTC (permalink / raw)
To: Holger Jakobs <holger@jakobs.com>; +Cc: pgsql-admin@lists.postgresql.org; rajeshkumar.dba09@gmail.com
Holger Jakobs <holger@jakobs.com> writes:
> Am 07.12.23 um 19:11 schrieb Rajesh Kumar:
>> Will pg_dump cause blocking queries? If so how to take dump without
>> blocking?
> Readers don't block writers, writers don't block readers in PostgreSQL.
> pg_dump is a reader.
To enlarge on that a bit: pg_dump takes AccessShareLock on every
table it intends to dump. This does not conflict with ordinary
DML updates. It *will* conflict with anything that wants
AccessExclusiveLock, which typically is schema-altering DDL.
See
https://www.postgresql.org/docs/current/explicit-locking.html#LOCKING-TABLES
So the answer to your question is "don't try to alter the
database schema while pg_dump is running". You can alter
database content freely, though.
regards, tom lane
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2023-12-07 19:00 M Sarwar <sarwarmd02@outlook.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 42+ messages in thread
From: M Sarwar @ 2023-12-07 19:00 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; Holger Jakobs <holger@jakobs.com>; +Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>; rajeshkumar.dba09@gmail.com <rajeshkumar.dba09@gmail.com>
I agree with Tom. This is making the difference. I ran into this scenario several times in the past.
But whole database is becoming slow when the dump is happening .
Thanks,
Sarwar
________________________________
From: Tom Lane <tgl@sss.pgh.pa.us>
Sent: Thursday, December 7, 2023 1:52 PM
To: Holger Jakobs <holger@jakobs.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>; rajeshkumar.dba09@gmail.com <rajeshkumar.dba09@gmail.com>
Subject: Re: Pg_dump
Holger Jakobs <holger@jakobs.com> writes:
> Am 07.12.23 um 19:11 schrieb Rajesh Kumar:
>> Will pg_dump cause blocking queries? If so how to take dump without
>> blocking?
> Readers don't block writers, writers don't block readers in PostgreSQL.
> pg_dump is a reader.
To enlarge on that a bit: pg_dump takes AccessShareLock on every
table it intends to dump. This does not conflict with ordinary
DML updates. It *will* conflict with anything that wants
AccessExclusiveLock, which typically is schema-altering DDL.
See
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.postgresql.org%2Fdocs%2Fcurrent...;
So the answer to your question is "don't try to alter the
database schema while pg_dump is running". You can alter
database content freely, though.
regards, tom lane
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2023-12-07 19:39 Alvaro Herrera <alvherre@alvh.no-ip.org>
parent: M Sarwar <sarwarmd02@outlook.com>
0 siblings, 0 replies; 42+ messages in thread
From: Alvaro Herrera @ 2023-12-07 19:39 UTC (permalink / raw)
To: M Sarwar <sarwarmd02@outlook.com>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; Holger Jakobs <holger@jakobs.com>; pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>; rajeshkumar.dba09@gmail.com <rajeshkumar.dba09@gmail.com>
On 2023-Dec-07, M Sarwar wrote:
> I agree with Tom. This is making the difference. I ran into this scenario several times in the past.
> But whole database is becoming slow when the dump is happening .
For large databases with very high rate of updates, a running pg_dump
can prevent vacuum from removing old versions of rows. This can make
the operations slower because of accumulation of bloat.
For such situations, pg_dump is not really recommended. It's better to
use a physical backup (say, pgbarman), or if you really need a pg_dump
output file for some reason, create a replica (with _no_
hot_standby_feedback) and run pg_dump there.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"I'm always right, but sometimes I'm more right than other times."
(Linus Torvalds)
https://lore.kernel.org/git/Pine.LNX.4.58.0504150753440.7211@ppc970.osdl.org/
^ permalink raw reply [nested|flat] 42+ messages in thread
* Pg_dump
@ 2023-12-07 19:52 Rajesh Kumar <rajeshkumar.dba09@gmail.com>
0 siblings, 3 replies; 42+ messages in thread
From: Rajesh Kumar @ 2023-12-07 19:52 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
I could see the side of table inside db is 24 gb.
I was taking dump and it is growing over 30gb. Then I stopped dump process
What coule be the issue?
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2023-12-07 19:55 David G. Johnston <david.g.johnston@gmail.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2 siblings, 0 replies; 42+ messages in thread
From: David G. Johnston @ 2023-12-07 19:55 UTC (permalink / raw)
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
On Thursday, December 7, 2023, Rajesh Kumar <rajeshkumar.dba09@gmail.com>
wrote:
> I could see the side of table inside db is 24 gb.
>
> I was taking dump and it is growing over 30gb. Then I stopped dump process
>
>
> What coule be the issue?
>
Non-compression of the dumped data? Maybe give some help and show the
commands you are using to check the size and perform the dump.
David J.
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2023-12-07 19:58 M Sarwar <sarwarmd02@outlook.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2 siblings, 1 reply; 42+ messages in thread
From: M Sarwar @ 2023-12-07 19:58 UTC (permalink / raw)
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
Luckily when I am taking a dump, database size is not growing. If the size grows, my dump will fail because it has no space left on my environment.
Thanks,
Sarwar
________________________________
From: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
Sent: Thursday, December 7, 2023 2:52 PM
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Pg_dump
I could see the side of table inside db is 24 gb.
I was taking dump and it is growing over 30gb. Then I stopped dump process
What coule be the issue?
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2023-12-07 20:00 jason cable <cablej2082@gmail.com>
parent: M Sarwar <sarwarmd02@outlook.com>
0 siblings, 1 reply; 42+ messages in thread
From: jason cable @ 2023-12-07 20:00 UTC (permalink / raw)
To: M Sarwar <sarwarmd02@outlook.com>; +Cc: Rajesh Kumar <rajeshkumar.dba09@gmail.com>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
do you feel the need to squeeze the big data through small hole for
verification?
On Thu, Dec 7, 2023 at 11:59 AM M Sarwar <sarwarmd02@outlook.com> wrote:
> Luckily when I am taking a dump, database size is not growing. If the
> size grows, my dump will fail because it has no space left on my
> environment.
> Thanks,
> Sarwar
>
> ------------------------------
> *From:* Rajesh Kumar <rajeshkumar.dba09@gmail.com>
> *Sent:* Thursday, December 7, 2023 2:52 PM
> *To:* Pgsql-admin <pgsql-admin@lists.postgresql.org>
> *Subject:* Pg_dump
>
> I could see the side of table inside db is 24 gb.
>
> I was taking dump and it is growing over 30gb. Then I stopped dump process
>
>
> What coule be the issue?
>
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2023-12-07 20:02 M Sarwar <sarwarmd02@outlook.com>
parent: jason cable <cablej2082@gmail.com>
0 siblings, 0 replies; 42+ messages in thread
From: M Sarwar @ 2023-12-07 20:02 UTC (permalink / raw)
To: jason cable <cablej2082@gmail.com>; +Cc: Rajesh Kumar <rajeshkumar.dba09@gmail.com>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
Jason,
Are you referring within the postgres database or are you referring to Big Data approach which needs new platforms?
________________________________
From: jason cable <cablej2082@gmail.com>
Sent: Thursday, December 7, 2023 3:00 PM
To: M Sarwar <sarwarmd02@outlook.com>
Cc: Rajesh Kumar <rajeshkumar.dba09@gmail.com>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Pg_dump
do you feel the need to squeeze the big data through small hole for verification?
On Thu, Dec 7, 2023 at 11:59 AM M Sarwar <sarwarmd02@outlook.com<mailto:sarwarmd02@outlook.com>> wrote:
Luckily when I am taking a dump, database size is not growing. If the size grows, my dump will fail because it has no space left on my environment.
Thanks,
Sarwar
________________________________
From: Rajesh Kumar <rajeshkumar.dba09@gmail.com<mailto:rajeshkumar.dba09@gmail.com>>
Sent: Thursday, December 7, 2023 2:52 PM
To: Pgsql-admin <pgsql-admin@lists.postgresql.org<mailto:pgsql-admin@lists.postgresql.org>>
Subject: Pg_dump
I could see the side of table inside db is 24 gb.
I was taking dump and it is growing over 30gb. Then I stopped dump process
What coule be the issue?
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: Pg_dump
@ 2023-12-07 21:31 Ron Johnson <ronljohnsonjr@gmail.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2 siblings, 0 replies; 42+ messages in thread
From: Ron Johnson @ 2023-12-07 21:31 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
On Thu, Dec 7, 2023 at 2:52 PM Rajesh Kumar <rajeshkumar.dba09@gmail.com>
wrote:
> I could see the side of table inside db is 24 gb.
>
> I was taking dump and it is growing over 30gb. Then I stopped dump process
>
>
> What coule be the issue?
>
The exact command you ran.
Since you didn't show us the whole command, with options, we can't tell you.
^ permalink raw reply [nested|flat] 42+ messages in thread
* pg_dump
@ 2024-08-12 19:09 Wasim Devale <wasimd60@gmail.com>
0 siblings, 2 replies; 42+ messages in thread
From: Wasim Devale @ 2024-08-12 19:09 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>; pgsql-admin
Hi All
Please let me know if the below option persists while using pg_dump command:
-t table_name --exclude-column column_name
I have a table with a column having bytea data type (BLOBS). I just want to
exclude this in the dump file as it is of 99GB but I want the other data in
the same table which is of only 22MB.
Please let me know any work around this.
I used this option in pg_dump but that didn't work:
--exclude-table-data = table_name
PG version 12.19
Thanks,
Wasim
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: pg_dump
@ 2024-08-12 19:16 David G. Johnston <david.g.johnston@gmail.com>
parent: Wasim Devale <wasimd60@gmail.com>
1 sibling, 0 replies; 42+ messages in thread
From: David G. Johnston @ 2024-08-12 19:16 UTC (permalink / raw)
To: Wasim Devale <wasimd60@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>; pgsql-admin
On Monday, August 12, 2024, Wasim Devale <wasimd60@gmail.com> wrote:
>
>
> Please let me know if the below option persists while using pg_dump
> command:
>
> -t table_name --exclude-column column_name
>
No, there is no option to dump a partial table, rows or columns.
>
> I just want to exclude this in the dump file as it is of 99GB but I want
> the other data in the same table which is of only 22MB.
>
> Please let me know any work around this.
>
Write your own copy command to export that table’s contents. See the
—snapshot option.
David J.
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: pg_dump
@ 2024-08-12 19:18 Holger Jakobs <holger@jakobs.com>
parent: Wasim Devale <wasimd60@gmail.com>
1 sibling, 1 reply; 42+ messages in thread
From: Holger Jakobs @ 2024-08-12 19:18 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Am 12.08.24 um 21:09 schrieb Wasim Devale:
> Hi All
>
> Please let me know if the below option persists while using pg_dump
> command:
>
> -t table_name --exclude-column column_name
>
> I have a table with a column having bytea data type (BLOBS). I just
> want to exclude this in the dump file as it is of 99GB but I want the
> other data in the same table which is of only 22MB.
>
> Please let me know any work around this.
>
> I used this option in pg_dump but that didn't work:
>
> --exclude-table-data = table_name
>
> PG version 12.19
>
> Thanks,
> Wasim
No, pg_dump can only dump complete tables.
An alternative would be exporting the result of a select command via
COPY or \copy to a file, which can easily be read again with COPY or \copy
COPY is an SQL command and has to be used by a superuser because it
writes to (or reads from) a file on the server.
\copy is a psql command and thus can only be executed in psql (not any
other client) and by any user, because it writes to (or reads from) a
file on the client computer.
Kind Regards,
Holger
--
Holger Jakobs, Bergisch Gladbach
Attachments:
[application/pgp-signature] OpenPGP_signature (202B, ../../7b149653-4992-9285-d9af-53929497f4e8@jakobs.com/2-OpenPGP_signature)
download
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: pg_dump
@ 2024-08-13 06:22 Wasim Devale <wasimd60@gmail.com>
parent: Holger Jakobs <holger@jakobs.com>
0 siblings, 2 replies; 42+ messages in thread
From: Wasim Devale @ 2024-08-13 06:22 UTC (permalink / raw)
To: Holger Jakobs <holger@jakobs.com>; +Cc: pgsql-admin@lists.postgresql.org
I did one thing, we can exclude the toast table in the pg_dump command that
has the BLOBS data for a particular table.
--exclude-table-data=pg_toast.pg_toast_10176226
Thanks,
Wasim
On Tue, 13 Aug, 2024, 12:48 am Holger Jakobs, <holger@jakobs.com> wrote:
> Am 12.08.24 um 21:09 schrieb Wasim Devale:
> > Hi All
> >
> > Please let me know if the below option persists while using pg_dump
> > command:
> >
> > -t table_name --exclude-column column_name
> >
> > I have a table with a column having bytea data type (BLOBS). I just
> > want to exclude this in the dump file as it is of 99GB but I want the
> > other data in the same table which is of only 22MB.
> >
> > Please let me know any work around this.
> >
> > I used this option in pg_dump but that didn't work:
> >
> > --exclude-table-data = table_name
> >
> > PG version 12.19
> >
> > Thanks,
> > Wasim
> No, pg_dump can only dump complete tables.
>
> An alternative would be exporting the result of a select command via
> COPY or \copy to a file, which can easily be read again with COPY or \copy
>
> COPY is an SQL command and has to be used by a superuser because it
> writes to (or reads from) a file on the server.
> \copy is a psql command and thus can only be executed in psql (not any
> other client) and by any user, because it writes to (or reads from) a
> file on the client computer.
>
> Kind Regards,
>
> Holger
>
> --
>
> Holger Jakobs, Bergisch Gladbach
>
>
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: pg_dump
@ 2024-08-13 06:22 Wasim Devale <wasimd60@gmail.com>
parent: Wasim Devale <wasimd60@gmail.com>
1 sibling, 0 replies; 42+ messages in thread
From: Wasim Devale @ 2024-08-13 06:22 UTC (permalink / raw)
To: Holger Jakobs <holger@jakobs.com>; +Cc: pgsql-admin@lists.postgresql.org
Please let me know your inputs.
On Tue, 13 Aug, 2024, 11:52 am Wasim Devale, <wasimd60@gmail.com> wrote:
> I did one thing, we can exclude the toast table in the pg_dump command
> that has the BLOBS data for a particular table.
>
> --exclude-table-data=pg_toast.pg_toast_10176226
>
> Thanks,
> Wasim
>
> On Tue, 13 Aug, 2024, 12:48 am Holger Jakobs, <holger@jakobs.com> wrote:
>
>> Am 12.08.24 um 21:09 schrieb Wasim Devale:
>> > Hi All
>> >
>> > Please let me know if the below option persists while using pg_dump
>> > command:
>> >
>> > -t table_name --exclude-column column_name
>> >
>> > I have a table with a column having bytea data type (BLOBS). I just
>> > want to exclude this in the dump file as it is of 99GB but I want the
>> > other data in the same table which is of only 22MB.
>> >
>> > Please let me know any work around this.
>> >
>> > I used this option in pg_dump but that didn't work:
>> >
>> > --exclude-table-data = table_name
>> >
>> > PG version 12.19
>> >
>> > Thanks,
>> > Wasim
>> No, pg_dump can only dump complete tables.
>>
>> An alternative would be exporting the result of a select command via
>> COPY or \copy to a file, which can easily be read again with COPY or \copy
>>
>> COPY is an SQL command and has to be used by a superuser because it
>> writes to (or reads from) a file on the server.
>> \copy is a psql command and thus can only be executed in psql (not any
>> other client) and by any user, because it writes to (or reads from) a
>> file on the client computer.
>>
>> Kind Regards,
>>
>> Holger
>>
>> --
>>
>> Holger Jakobs, Bergisch Gladbach
>>
>>
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: pg_dump
@ 2024-08-13 06:33 Tom Lane <tgl@sss.pgh.pa.us>
parent: Wasim Devale <wasimd60@gmail.com>
1 sibling, 1 reply; 42+ messages in thread
From: Tom Lane @ 2024-08-13 06:33 UTC (permalink / raw)
To: Wasim Devale <wasimd60@gmail.com>; +Cc: Holger Jakobs <holger@jakobs.com>; pgsql-admin@lists.postgresql.org
Wasim Devale <wasimd60@gmail.com> writes:
> I did one thing, we can exclude the toast table in the pg_dump command that
> has the BLOBS data for a particular table.
> --exclude-table-data=pg_toast.pg_toast_10176226
Utterly pointless. pg_dump does not dump toast tables as such;
it's only concerned with their parent "regular" tables. It will
fetch data from the regular tables, and it's not concerned with
the server-side implementation detail that some of that data
might be coming out of a toast table.
regards, tom lane
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: pg_dump
@ 2024-08-13 06:42 Wasim Devale <wasimd60@gmail.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 3 replies; 42+ messages in thread
From: Wasim Devale @ 2024-08-13 06:42 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Holger Jakobs <holger@jakobs.com>; pgsql-admin@lists.postgresql.org
Then what might be the solution for it if I am only concerned about using
pg_dump
On Tue, 13 Aug, 2024, 12:03 pm Tom Lane, <tgl@sss.pgh.pa.us> wrote:
> Wasim Devale <wasimd60@gmail.com> writes:
> > I did one thing, we can exclude the toast table in the pg_dump command
> that
> > has the BLOBS data for a particular table.
> > --exclude-table-data=pg_toast.pg_toast_10176226
>
> Utterly pointless. pg_dump does not dump toast tables as such;
> it's only concerned with their parent "regular" tables. It will
> fetch data from the regular tables, and it's not concerned with
> the server-side implementation detail that some of that data
> might be coming out of a toast table.
>
> regards, tom lane
>
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: pg_dump
@ 2024-08-13 12:04 Ron Johnson <ronljohnsonjr@gmail.com>
parent: Wasim Devale <wasimd60@gmail.com>
2 siblings, 0 replies; 42+ messages in thread
From: Ron Johnson @ 2024-08-13 12:04 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
"Free your mind, and *pg_dump* will follow." Maybe *En Vogue*, but
probably not.
On Tue, Aug 13, 2024 at 2:43 AM Wasim Devale <wasimd60@gmail.com> wrote:
> Then what might be the solution for it if I am only concerned about using
> pg_dump
>
> On Tue, 13 Aug, 2024, 12:03 pm Tom Lane, <tgl@sss.pgh.pa.us> wrote:
>
>> Wasim Devale <wasimd60@gmail.com> writes:
>> > I did one thing, we can exclude the toast table in the pg_dump command
>> that
>> > has the BLOBS data for a particular table.
>> > --exclude-table-data=pg_toast.pg_toast_10176226
>>
>> Utterly pointless. pg_dump does not dump toast tables as such;
>> it's only concerned with their parent "regular" tables. It will
>> fetch data from the regular tables, and it's not concerned with
>> the server-side implementation detail that some of that data
>> might be coming out of a toast table.
>>
>> regards, tom lane
>>
>
--
Death to America, and butter sauce.
Iraq lobster!
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: pg_dump
@ 2024-08-13 12:05 Ron Johnson <ronljohnsonjr@gmail.com>
parent: Wasim Devale <wasimd60@gmail.com>
2 siblings, 0 replies; 42+ messages in thread
From: Ron Johnson @ 2024-08-13 12:05 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Oops... should have been "free your mind, and COPY will follow."
On Tue, Aug 13, 2024 at 2:43 AM Wasim Devale <wasimd60@gmail.com> wrote:
> Then what might be the solution for it if I am only concerned about using
> pg_dump
>
> On Tue, 13 Aug, 2024, 12:03 pm Tom Lane, <tgl@sss.pgh.pa.us> wrote:
>
>> Wasim Devale <wasimd60@gmail.com> writes:
>> > I did one thing, we can exclude the toast table in the pg_dump command
>> that
>> > has the BLOBS data for a particular table.
>> > --exclude-table-data=pg_toast.pg_toast_10176226
>>
>> Utterly pointless. pg_dump does not dump toast tables as such;
>> it's only concerned with their parent "regular" tables. It will
>> fetch data from the regular tables, and it's not concerned with
>> the server-side implementation detail that some of that data
>> might be coming out of a toast table.
>>
>> regards, tom lane
>>
>
--
Death to America, and butter sauce.
Iraq lobster!
^ permalink raw reply [nested|flat] 42+ messages in thread
* Re: pg_dump
@ 2024-08-13 12:35 David G. Johnston <david.g.johnston@gmail.com>
parent: Wasim Devale <wasimd60@gmail.com>
2 siblings, 0 replies; 42+ messages in thread
From: David G. Johnston @ 2024-08-13 12:35 UTC (permalink / raw)
To: Wasim Devale <wasimd60@gmail.com>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; Holger Jakobs <holger@jakobs.com>; pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
On Monday, August 12, 2024, Wasim Devale <wasimd60@gmail.com> wrote:
> Then what might be the solution for it if I am only concerned about using
> pg_dump
>
Create a new table to house the bytea data, copy the bytea data to it, drop
the bytea column from the existing table.
David J.
^ permalink raw reply [nested|flat] 42+ messages in thread
end of thread, other threads:[~2024-08-13 12:35 UTC | newest]
Thread overview: 42+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-08-04 08:43 pg_dump julien piaser <jpiaser@lxsolutions.com>
2002-07-19 20:53 pg_dump Robson Martins <robson-martins@bol.com.br>
2003-12-31 08:01 PG_DUMP omkar prabhu <oprabhu@phildigital.com>
2004-12-26 10:09 Pg_dump Gourish Singbal <gourish@gmail.com>
2004-12-26 17:47 ` Re: Pg_dump Bruno Wolff III <bruno@wolff.to>
2004-12-26 23:33 ` Re: Pg_dump Tom Lane <tgl@sss.pgh.pa.us>
2004-12-28 15:55 ` Re: Pg_dump Gourish Singbal <gourish@gmail.com>
2004-12-27 14:27 Re: Pg_dump Spiegelberg, Greg <gspiegelberg@cranel.com>
2004-12-27 21:01 ` Re: Pg_dump Bruno Wolff III <bruno@wolff.to>
2005-10-10 05:30 pg_dump Nirav Parikh <nirav.p@workskillsprofessionals.com.au>
2005-10-10 06:48 ` Luca Ferrari <fluca1978@infinito.it>
2006-05-26 04:50 PG_DUMP renneyt@yahoo.com <renneyt@yahoo.com>
2006-05-26 13:45 ` Re: PG_DUMP Jeff Boes <jeff@endpoint.com>
2015-12-23 22:27 pg_dump Artem Tomyuk <admin@leboutique.com>
2015-12-23 22:29 ` Artem Tomyuk <admin@leboutique.com>
2021-12-07 07:08 Pg_dump Firthouse banu <penguinsfairy@gmail.com>
2021-12-07 12:55 ` Re: Pg_dump David G. Johnston <david.g.johnston@gmail.com>
2021-12-07 14:18 ` Re: Pg_dump Mladen Gogala <gogala.mladen@gmail.com>
2021-12-07 15:06 ` Re: Pg_dump Scott Ribe <scott_ribe@elevated-dev.com>
2023-12-07 18:11 Pg_dump Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2023-12-07 18:13 ` Re: Pg_dump Holger Jakobs <holger@jakobs.com>
2023-12-07 18:26 ` Re: Pg_dump Scott Ribe <scott_ribe@elevated-dev.com>
2023-12-07 18:39 ` Re: Pg_dump jason cable <cablej2082@gmail.com>
2023-12-07 18:52 ` Re: Pg_dump Tom Lane <tgl@sss.pgh.pa.us>
2023-12-07 19:00 ` Re: Pg_dump M Sarwar <sarwarmd02@outlook.com>
2023-12-07 19:39 ` Re: Pg_dump Alvaro Herrera <alvherre@alvh.no-ip.org>
2023-12-07 19:52 Pg_dump Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2023-12-07 19:55 ` Re: Pg_dump David G. Johnston <david.g.johnston@gmail.com>
2023-12-07 19:58 ` Re: Pg_dump M Sarwar <sarwarmd02@outlook.com>
2023-12-07 20:00 ` Re: Pg_dump jason cable <cablej2082@gmail.com>
2023-12-07 20:02 ` Re: Pg_dump M Sarwar <sarwarmd02@outlook.com>
2023-12-07 21:31 ` Re: Pg_dump Ron Johnson <ronljohnsonjr@gmail.com>
2024-08-12 19:09 pg_dump Wasim Devale <wasimd60@gmail.com>
2024-08-12 19:16 ` David G. Johnston <david.g.johnston@gmail.com>
2024-08-12 19:18 ` Holger Jakobs <holger@jakobs.com>
2024-08-13 06:22 ` Wasim Devale <wasimd60@gmail.com>
2024-08-13 06:22 ` Wasim Devale <wasimd60@gmail.com>
2024-08-13 06:33 ` Tom Lane <tgl@sss.pgh.pa.us>
2024-08-13 06:42 ` Wasim Devale <wasimd60@gmail.com>
2024-08-13 12:04 ` Ron Johnson <ronljohnsonjr@gmail.com>
2024-08-13 12:05 ` Ron Johnson <ronljohnsonjr@gmail.com>
2024-08-13 12:35 ` David G. Johnston <david.g.johnston@gmail.com>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox