pg.ddx.io pgsql-general@postgresql.org mailing list archive
help / color / mirror / Atom feedUpgrading to v12
31+ messages / 4 participants
[nested] [flat]
* Upgrading to v12
@ 2022-11-11 20:43 Brad White <b55white@gmail.com>
0 siblings, 1 reply; 31+ messages in thread
From: Brad White @ 2022-11-11 20:43 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org
I'm upgrading from v9.4 to v12.10 as a half step to 15.
Q1: How do I tell it which database to upgrade?
I only need the primary.
Not the half dozen restored copies.
Or do I need to detach everything I don't want copied?
Q2: I get this error, and then at the end, it says "No error."
Performing Consistency Checks
-----------------------------
Checking cluster versions ok
SQL command failed
WITH regular_heap (reloid, indtable, toastheap) AS ( SELECT c.oid,
0::oid, 0::oid FROM pg_catalog.pg_class c JOIN pg_catalog.pg_namespace n
ON c.relnamespace = n.oid WHERE relkind IN ('r', 'm') AND
((n.nspname !~ '^pg_temp_' AND n.nspname !~ '^pg_toast_temp_' AND
n.nspname NOT IN ('pg_catalog', 'information_schema',
'binary_upgrade', 'pg_toast') AND c.oid >= 16384::pg_catalog.oid)
OR (n.nspname = 'pg_catalog' AND relname IN ('pg_largeobject')
))), toast_heap (reloid, indtable, toastheap) AS ( SELECT
c.reltoastrelid, 0::oid, c.oid FROM regular_heap JOIN pg_catalog.pg_class
c ON regular_heap.reloid = c.oid WHERE c.reltoastrelid != 0),
all_index (reloid, indtable, toastheap) AS ( SELECT indexrelid, indrelid,
0::oid FROM pg_catalog.pg_index WHERE indisvalid AND indisready AND
indrelid IN (SELECT reloid FROM regular_heap UNION ALL
SELECT reloid FROM toast_heap)) SELECT all_rels.*, n.nspname,
c.relname, c.relfilenode, c.reltablespace,
pg_catalog.pg_tablespace_location(t.oid) AS spclocation FROM (SELECT * FROM
regular_heap UNION ALL SELECT * FROM toast_heap UNION ALL
SELECT * FROM all_index) all_rels JOIN pg_catalog.pg_class c
ON all_rels.reloid = c.oid JOIN pg_catalog.pg_namespace n ON
c.relnamespace = n.oid LEFT OUTER JOIN pg_catalog.pg_tablespace t ON
c.reltablespace = t.oid ORDER BY 1;
ERROR: could not access status of transaction 22316920
DETAIL: Could not read from file "pg_clog/0015" at offset 73728: No error.
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-11 21:02 Adrian Klaver <adrian.klaver@aklaver.com>
parent: Brad White <b55white@gmail.com>
0 siblings, 1 reply; 31+ messages in thread
From: Adrian Klaver @ 2022-11-11 21:02 UTC (permalink / raw)
To: Brad White <b55white@gmail.com>; pgsql-general@lists.postgresql.org
On 11/11/22 12:43, Brad White wrote:
> I'm upgrading from v9.4 to v12.10 as a half step to 15.
>
> Q1: How do I tell it which database to upgrade?
> I only need the primary.
> Not the half dozen restored copies.
> Or do I need to detach everything I don't want copied?
1) If you are using pg_upgrade then it only works on the entire cluster
not individual databases.
2) This is not SQLite there is no detaching of databases.
3) I you want to move a single database then you are looking at
pg_dump/pg_restore or logical replication.
>
> Q2: I get this error, and then at the end, it says "No error."
What was the complete pg_upgrade command you used?
>
> Performing Consistency Checks
> -----------------------------
> Checking cluster versions ok
> SQL command failed
> WITH regular_heap (reloid, indtable, toastheap) AS ( SELECT c.oid,
> 0::oid, 0::oid FROM pg_catalog.pg_class c JOIN pg_catalog.pg_namespace
> n ON c.relnamespace = n.oid WHERE relkind IN ('r', 'm') AND
> ((n.nspname !~ '^pg_temp_' AND n.nspname !~ '^pg_toast_temp_'
> AND n.nspname NOT IN ('pg_catalog', 'information_schema',
> 'binary_upgrade', 'pg_toast') AND c.oid >=
> 16384::pg_catalog.oid) OR (n.nspname = 'pg_catalog' AND
> relname IN ('pg_largeobject') ))), toast_heap (reloid, indtable,
> toastheap) AS ( SELECT c.reltoastrelid, 0::oid, c.oid FROM
> regular_heap JOIN pg_catalog.pg_class c ON regular_heap.reloid =
> c.oid WHERE c.reltoastrelid != 0), all_index (reloid, indtable,
> toastheap) AS ( SELECT indexrelid, indrelid, 0::oid FROM
> pg_catalog.pg_index WHERE indisvalid AND indisready AND indrelid
> IN (SELECT reloid FROM regular_heap UNION ALL
> SELECT reloid FROM toast_heap)) SELECT all_rels.*, n.nspname,
> c.relname, c.relfilenode, c.reltablespace,
> pg_catalog.pg_tablespace_location(t.oid) AS spclocation FROM (SELECT *
> FROM regular_heap UNION ALL SELECT * FROM toast_heap
> UNION ALL SELECT * FROM all_index) all_rels JOIN
> pg_catalog.pg_class c ON all_rels.reloid = c.oid JOIN
> pg_catalog.pg_namespace n ON c.relnamespace = n.oid LEFT OUTER
> JOIN pg_catalog.pg_tablespace t ON c.reltablespace = t.oid ORDER BY 1;
> ERROR: could not access status of transaction 22316920
> DETAIL: Could not read from file "pg_clog/0015" at offset 73728: No error.
--
Adrian Klaver
adrian.klaver@aklaver.com
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-11 21:05 Brad White <b55white@gmail.com>
parent: Adrian Klaver <adrian.klaver@aklaver.com>
0 siblings, 1 reply; 31+ messages in thread
From: Brad White @ 2022-11-11 21:05 UTC (permalink / raw)
To: Adrian Klaver <adrian.klaver@aklaver.com>; +Cc: pgsql-general@lists.postgresql.org
> What was the complete pg_upgrade command you used?
"C:\Program Files\PostgreSQL\12\bin\pg_upgrade" -d "C:\Program
Files\PostgreSQL\9.4\data" -D "C:\Program Files\PostgreSQL\12\data" -b
"C:\Program Files\PostgreSQL\9.4\bin" -B "C:\Program
Files\PostgreSQL\12\bin" -U postgres -p 5432 -P 5435
>
>
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-11 21:11 Brad White <b55white@gmail.com>
parent: Brad White <b55white@gmail.com>
0 siblings, 2 replies; 31+ messages in thread
From: Brad White @ 2022-11-11 21:11 UTC (permalink / raw)
To: ; +Cc: pgsql-general@lists.postgresql.org
I deleted all the other DBs and left only the primary.
Still getting the same error message, ending with
ERROR: could not access status of transaction 22316920
DETAIL: Could not read from file "pg_clog/0015" at offset 73728: No error.
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-11 21:16 Tom Lane <tgl@sss.pgh.pa.us>
parent: Brad White <b55white@gmail.com>
1 sibling, 0 replies; 31+ messages in thread
From: Tom Lane @ 2022-11-11 21:16 UTC (permalink / raw)
To: Brad White <b55white@gmail.com>; +Cc: pgsql-general@lists.postgresql.org
Brad White <b55white@gmail.com> writes:
> I deleted all the other DBs and left only the primary.
> Still getting the same error message, ending with
> ERROR: could not access status of transaction 22316920
> DETAIL: Could not read from file "pg_clog/0015" at offset 73728: No error.
That's a pretty clear indication of data corruption. pg_upgrade
isn't going to be able to work with a corrupted source database,
so you'll have to do something to clear that before you can get
anywhere.
There's some advice about dealing with that here:
https://wiki.postgresql.org/wiki/Corruption
but in general the news is not going to be good.
regards, tom lane
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-11 21:17 Adrian Klaver <adrian.klaver@aklaver.com>
parent: Brad White <b55white@gmail.com>
1 sibling, 2 replies; 31+ messages in thread
From: Adrian Klaver @ 2022-11-11 21:17 UTC (permalink / raw)
To: Brad White <b55white@gmail.com>; +Cc: pgsql-general@lists.postgresql.org
On 11/11/22 13:11, Brad White wrote:
> I deleted all the other DBs and left only the primary.
> Still getting the same error message, ending with
>
> ERROR: could not access status of transaction 22316920
> DETAIL: Could not read from file "pg_clog/0015" at offset 73728: No error.
Can you do a pg_dump of that database?
--
Adrian Klaver
adrian.klaver@aklaver.com
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-11 21:42 Brad White <b55white@gmail.com>
parent: Adrian Klaver <adrian.klaver@aklaver.com>
1 sibling, 2 replies; 31+ messages in thread
From: Brad White @ 2022-11-11 21:42 UTC (permalink / raw)
To: Adrian Klaver <adrian.klaver@aklaver.com>; +Cc: pgsql-general@lists.postgresql.org
I'm practicing on our Dev server, so I can blow this away and reload at any
time.
Are there any utilities to check for corruption on my Prod server in v9.4.1?
All my backups are done with pg_dump.exe, so that's where this database
came from in the first place.
So we know that pg_dump.exe works on Prod at least.
On Fri, Nov 11, 2022 at 3:17 PM Adrian Klaver <adrian.klaver@aklaver.com>
wrote:
> On 11/11/22 13:11, Brad White wrote:
> > I deleted all the other DBs and left only the primary.
> > Still getting the same error message, ending with
> >
> > ERROR: could not access status of transaction 22316920
> > DETAIL: Could not read from file "pg_clog/0015" at offset 73728: No
> error.
>
> Can you do a pg_dump of that database?
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
>
>
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-11 22:06 Brad White <b55white@gmail.com>
parent: Adrian Klaver <adrian.klaver@aklaver.com>
1 sibling, 2 replies; 31+ messages in thread
From: Brad White @ 2022-11-11 22:06 UTC (permalink / raw)
To: ; +Cc: pgsql-general@lists.postgresql.org
> Can you do a pg_dump of that database?
Yes. No visible problems. No errors reported.
On Fri, Nov 11, 2022 at 3:17 PM Adrian Klaver <adrian.klaver@aklaver.com>
wrote:
> On 11/11/22 13:11, Brad White wrote:
> > I deleted all the other DBs and left only the primary.
> > Still getting the same error message, ending with
> >
> > ERROR: could not access status of transaction 22316920
> > DETAIL: Could not read from file "pg_clog/0015" at offset 73728: No
> error.
>
> Can you do a pg_dump of that database?
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
>
>
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-11 22:27 Tom Lane <tgl@sss.pgh.pa.us>
parent: Brad White <b55white@gmail.com>
1 sibling, 1 reply; 31+ messages in thread
From: Tom Lane @ 2022-11-11 22:27 UTC (permalink / raw)
To: Brad White <b55white@gmail.com>; +Cc: pgsql-general@lists.postgresql.org
Brad White <b55white@gmail.com> writes:
>> Can you do a pg_dump of that database?
> Yes. No visible problems. No errors reported.
Well, that's quite interesting, because pg_dump ought to read
all the same catalogs that pg_upgrade is failing to read.
So I'm not quite sure what's going on there. Nonetheless,
your path forward is clear: use pg_dump (or better pg_dumpall)
and then load the output into a freshly initdb'd v12 installation.
It'll be a bit slower than the pg_upgrade way, but it'll work.
regards, tom lane
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-12 00:11 Adrian Klaver <adrian.klaver@aklaver.com>
parent: Brad White <b55white@gmail.com>
1 sibling, 0 replies; 31+ messages in thread
From: Adrian Klaver @ 2022-11-12 00:11 UTC (permalink / raw)
To: Brad White <b55white@gmail.com>; +Cc: pgsql-general@lists.postgresql.org
On 11/11/22 14:06, Brad White wrote:
> > Can you do a pg_dump of that database?
> Yes. No visible problems. No errors reported.
From your original post, what did "Not the half dozen restored copies"
mean?
In other words define the restore process.
--
Adrian Klaver
adrian.klaver@aklaver.com
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-12 02:41 Brad White <b55white@gmail.com>
parent: Brad White <b55white@gmail.com>
1 sibling, 2 replies; 31+ messages in thread
From: Brad White @ 2022-11-12 02:41 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org
> From your original post, what did "Not the half dozen restored copies"
mean?
Over time, we've restored multiple copies for testing and reproducing
various issues.
I'm only trying to set up replication one one of those copies.
> In other words define the restore process.
Command to back up the database:
"C:\Program Files\PostgreSQL\9.4\bin\pg_dump.exe" --host localhost --port
5432 --username "postgres" --no-password --format custom --blobs --verbose
--file "DB_"%datestr%"\DB_"%datestr%.backup "DB"
Restore:
$pgdir\pg_restore.exe -h localhost -p 5433 -U postgres --no-password
--clean --if-exists --format=custom --dbname="DB_test"
"C:\Temp\DB_20220922_2300\DB_20220922_2300.backup"
The errors looked insignificant to me. The database comes up and appears to
be perfectly functional.
pg_restore.exe : pg_restore: while INITIALIZING:
At C:\Temp\Restore12.ps1:36 char:2
+ &$prestore -h $phost -p $pport -U postgres --no-password --clean
--if-exists -- ...
+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (pg_restore: while
INITIALIZING::String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
pg_restore: error:
could not execute query: ERROR: unrecognized configuration parameter
"idle_in_transaction_session_timeout"
Command was: SET idle_in_transaction_session_timeout = 0;
(Note: This is a backup from 9, being restored to 12. I assume that
pg_restore: error:
could not execute query: ERROR: unrecognized configuration parameter
"row_security"
Command was: SET row_security = off;
pg_restore
: WARNING: column "Button2" has type "unknown"
DETAIL: Proceeding with relation creation anyway.
pg_restore: WARNING: column "Button3" has type "unknown"
DETAIL: Proceeding with relation creation anyway.
pg_restore
: WARNING: column "Button4" has type "unknown"
DETAIL: Proceeding with relation creation anyway.
pg_restore: WARNING: column "Button5" has type "unknown"
DETAIL: Proceeding with relation creation anyway.
pg_restore
: WARNING: column "Button6" has type "unknown"
DETAIL: Proceeding with relation creation anyway.
pg_restore
: WARNING: column "Button7" has type "unknown"
DETAIL: Proceeding with relation creation anyway.
pg_restore
: warning: errors ignored on restore: 2
On Fri, Nov 11, 2022 at 3:42 PM Brad White <b55white@gmail.com> wrote:
> I'm practicing on our Dev server, so I can blow this away and reload at
> any time.
> Are there any utilities to check for corruption on my Prod server in
> v9.4.1?
>
> All my backups are done with pg_dump.exe, so that's where this database
> came from in the first place.
> So we know that pg_dump.exe works on Prod at least.
>
> On Fri, Nov 11, 2022 at 3:17 PM Adrian Klaver <adrian.klaver@aklaver.com>
> wrote:
>
>> On 11/11/22 13:11, Brad White wrote:
>> > I deleted all the other DBs and left only the primary.
>> > Still getting the same error message, ending with
>> >
>> > ERROR: could not access status of transaction 22316920
>> > DETAIL: Could not read from file "pg_clog/0015" at offset 73728: No
>> error.
>>
>> Can you do a pg_dump of that database?
>>
>>
>> --
>> Adrian Klaver
>> adrian.klaver@aklaver.com
>>
>>
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-12 02:43 Brad White <b55white@gmail.com>
parent: Brad White <b55white@gmail.com>
1 sibling, 0 replies; 31+ messages in thread
From: Brad White @ 2022-11-12 02:43 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org
Sorry. Ignore the errors. That was mistakenly copied in from elsewhere.
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-12 03:57 Adrian Klaver <adrian.klaver@aklaver.com>
parent: Brad White <b55white@gmail.com>
1 sibling, 1 reply; 31+ messages in thread
From: Adrian Klaver @ 2022-11-12 03:57 UTC (permalink / raw)
To: Brad White <b55white@gmail.com>; pgsql-general@lists.postgresql.org
On 11/11/22 18:41, Brad White wrote:
> > From your original post, what did "Not the half dozen restored copies"
> mean?
> Over time, we've restored multiple copies for testing and reproducing
> various issues.
>
> I'm only trying to set up replication one one of those copies.
>
> > In other words define the restore process.
>
> Command to back up the database:
> "C:\Program Files\PostgreSQL\9.4\bin\pg_dump.exe" --host localhost
> --port 5432 --username "postgres" --no-password --format custom --blobs
> --verbose --file "DB_"%datestr%"\DB_"%datestr%.backup "DB"
>
> Restore:
> $pgdir\pg_restore.exe -h localhost -p 5433 -U postgres --no-password
> --clean --if-exists --format=custom --dbname="DB_test"
> "C:\Temp\DB_20220922_2300\DB_20220922_2300.backup"
Alright I am confused. You said you had multiple copies of the database
on one cluster. The above though shows you restoring to different
cluster(5433) then the cluster(5432) you dumped from.
Also why
"C:\Program Files\PostgreSQL\9.4\bin\pg_dump.exe
vs
$pgdir\pg_restore.exe
?
Is pgdir different from "C:\Program Files\PostgreSQL\9.4\bin\ ?
--
Adrian Klaver
adrian.klaver@aklaver.com
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-12 04:59 Brad White <b55white@gmail.com>
parent: Adrian Klaver <adrian.klaver@aklaver.com>
0 siblings, 1 reply; 31+ messages in thread
From: Brad White @ 2022-11-12 04:59 UTC (permalink / raw)
To: Adrian Klaver <adrian.klaver@aklaver.com>; +Cc: pgsql-general@lists.postgresql.org
On Fri, Nov 11, 2022, 9:57 PM Adrian Klaver <adrian.klaver@aklaver.com>
wrote:
> On 11/11/22 18:41, Brad White wrote:
> > > From your original post, what did "Not the half dozen restored copies"
> > mean?
> > Over time, we've restored multiple copies for testing and reproducing
> > various issues.
> >
> > I'm only trying to set up replication one one of those copies.
> >
> > > In other words define the restore process.
> >
> > Command to back up the database:
> > "C:\Program Files\PostgreSQL\9.4\bin\pg_dump.exe" --host localhost
> > --port 5432 --username "postgres" --no-password --format custom --blobs
> > --verbose --file "DB_"%datestr%"\DB_"%datestr%.backup "DB"
> >
> > Restore:
> > $pgdir\pg_restore.exe -h localhost -p 5433 -U postgres --no-password
> > --clean --if-exists --format=custom --dbname="DB_test"
> > "C:\Temp\DB_20220922_2300\DB_20220922_2300.backup"
>
> Alright I am confused. You said you had multiple copies of the database
> on one cluster.
yes. They've been deleted now, but we did.
The above though shows you restoring to different
> cluster(5433) then the cluster(5432) you dumped from.
>
Yes. The backup is from production.
V9.4 is running on 5432 on all servers.
That particular restore happens to be on the dev server. 5433 is v12.
>
> Also why
>
> "C:\Program Files\PostgreSQL\9.4\bin\pg_dump.exe
>
> vs
>
> $pgdir\pg_restore.exe
> ?
>
> Is pgdir different from "C:\Program Files\PostgreSQL\9.4\bin\ ?
>
"C:\Program Files... is from the backup script. Production is always only
on one version.
$pgdir is from the restore script.
So it might be
PostgreSQL\9.4\bin
or
PostgreSQL\12\bin
or
PostgreSQL\15\bin
Turns out that it doesn’t work well to mix the exe from one and the port
from another.
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
>
>
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-12 05:09 Adrian Klaver <adrian.klaver@aklaver.com>
parent: Brad White <b55white@gmail.com>
0 siblings, 3 replies; 31+ messages in thread
From: Adrian Klaver @ 2022-11-12 05:09 UTC (permalink / raw)
To: Brad White <b55white@gmail.com>; +Cc: pgsql-general@lists.postgresql.org
On 11/11/22 20:59, Brad White wrote:
> On Fri, Nov 11, 2022, 9:57 PM Adrian Klaver <adrian.klaver@aklaver.com
> <mailto:adrian.klaver@aklaver.com>> wrote:
> Yes. The backup is from production.
> V9.4 is running on 5432 on all servers.
> That particular restore happens to be on the dev server. 5433 is v12.
>
1) This does not address from your OP:
"I only need the primary.
Not the half dozen restored copies."
And then from follow up post:
"I deleted all the other DBs and left only the primary.
Still getting the same error message, ending with"
How where the restored copies made on the original cluster?
2) For your explanation above, pg_dump from 9.4(5432) to pg_restore
12(5433) the issue would be ...\9.4\bin\pg_dump.exe of 9.4 and
pg_restore of said dump file to version 12. When moving up in version
you need to use the newer version of pg_dump(...\12\bin\pg_dump.exe) to
dump the 9.4 instance and then the version 12 pg_restore to the 12
instance. Both programs are backwards compatible, not forwards compatible.
--
Adrian Klaver
adrian.klaver@aklaver.com
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-12 08:44 Ron <ronljohnsonjr@gmail.com>
parent: Brad White <b55white@gmail.com>
1 sibling, 2 replies; 31+ messages in thread
From: Ron @ 2022-11-12 08:44 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org
Step #1: upgrade to 9.4.26. You'll get *five years* of bug fixes.
(If the client lets you, of course. I had servers stuck on 8.4.17 and 9.2.7
that were only upgraded because PCI auditors were going to tell my client's
client, and that scared /my/ client. Now they're on 9.6.24...)
On 11/11/22 15:42, Brad White wrote:
> I'm practicing on our Dev server, so I can blow this away and reload at
> any time.
> Are there any utilities to check for corruption on my Prod server in v9.4.1?
>
> All my backups are done with pg_dump.exe, so that's where this database
> came from in the first place.
> So we know that pg_dump.exe works on Prod at least.
>
> On Fri, Nov 11, 2022 at 3:17 PM Adrian Klaver <adrian.klaver@aklaver.com>
> wrote:
>
> On 11/11/22 13:11, Brad White wrote:
> > I deleted all the other DBs and left only the primary.
> > Still getting the same error message, ending with
> >
> > ERROR: could not access status of transaction 22316920
> > DETAIL: Could not read from file "pg_clog/0015" at offset 73728: No
> error.
>
> Can you do a pg_dump of that database?
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
>
--
Angular momentum makes the world go 'round.
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-13 02:06 Brad White <b55white@gmail.com>
parent: Adrian Klaver <adrian.klaver@aklaver.com>
2 siblings, 0 replies; 31+ messages in thread
From: Brad White @ 2022-11-13 02:06 UTC (permalink / raw)
To: Adrian Klaver <adrian.klaver@aklaver.com>; +Cc: pgsql-general@lists.postgresql.org
> When moving up in version you need to use the newer version of
pg_dump(...\12\bin\pg_dump.exe) to dump the 9.4 instance and then the
version 12 pg_restore to the 12 instance.
Oh my. That's a substantial change that could make a difference.
Thanks for catching that.
>
>
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-13 02:07 Brad White <b55white@gmail.com>
parent: Ron <ronljohnsonjr@gmail.com>
1 sibling, 0 replies; 31+ messages in thread
From: Brad White @ 2022-11-13 02:07 UTC (permalink / raw)
To: Ron <ronljohnsonjr@gmail.com>; +Cc: pgsql-general@lists.postgresql.org
> Step #1: upgrade to 9.4.26. You'll get *five years* of bug fixes.
Good idea.
I'll try 12 first, and if that doesn't work we'll go with this.
>
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-13 02:12 Brad White <b55white@gmail.com>
parent: Ron <ronljohnsonjr@gmail.com>
1 sibling, 0 replies; 31+ messages in thread
From: Brad White @ 2022-11-13 02:12 UTC (permalink / raw)
To: Ron <ronljohnsonjr@gmail.com>; +Cc: pgsql-general@lists.postgresql.org
> If the client lets you, of course.
Right? 8: -)
That's not a concern here.
A) They trust me, and
B) They only see the front end. They don't really care what happens with
the back end.
so long as
A) It doesn't break, and
B) We get replication working.
>
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-13 02:18 Brad White <b55white@gmail.com>
parent: Adrian Klaver <adrian.klaver@aklaver.com>
2 siblings, 2 replies; 31+ messages in thread
From: Brad White @ 2022-11-13 02:18 UTC (permalink / raw)
To: Adrian Klaver <adrian.klaver@aklaver.com>; +Cc: pgsql-general@lists.postgresql.org
>
>
> > How where the restored copies made on the original cluster?
> I guess I'm not understanding the confusion here. They were restored with
> the same script but to a different DB name and with the 9.4 executables.
> In fact, that was why the script was originally written, so we could
> restore and test the backups.
>
> I've since hijacked it and used it to restore to other versions.
>
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-13 05:30 Ron <ronljohnsonjr@gmail.com>
parent: Adrian Klaver <adrian.klaver@aklaver.com>
2 siblings, 1 reply; 31+ messages in thread
From: Ron @ 2022-11-13 05:30 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org
On 11/11/22 23:09, Adrian Klaver wrote:
> On 11/11/22 20:59, Brad White wrote:
>> On Fri, Nov 11, 2022, 9:57 PM Adrian Klaver <adrian.klaver@aklaver.com
>> <mailto:adrian.klaver@aklaver.com>> wrote:
>
>> Yes. The backup is from production.
>> V9.4 is running on 5432 on all servers.
>> That particular restore happens to be on the dev server. 5433 is v12.
>>
>
> 1) This does not address from your OP:
>
> "I only need the primary.
> Not the half dozen restored copies."
>
> And then from follow up post:
>
> "I deleted all the other DBs and left only the primary.
> Still getting the same error message, ending with"
>
> How where the restored copies made on the original cluster?
>
> 2) For your explanation above, pg_dump from 9.4(5432) to pg_restore
> 12(5433) the issue would be ...\9.4\bin\pg_dump.exe of 9.4 and pg_restore
> of said dump file to version 12. When moving up in version you need to use
> the newer version of pg_dump(...\12\bin\pg_dump.exe) to dump the 9.4
> instance and then the version 12 pg_restore to the 12 instance. Both
> programs are backwards compatible, not forwards compatible.
Unless there's some bug (you're running a /really/ old version of 9.4), you
might be able to get away with using the 9.4 binary. (I successfully
migrated 8.4.17 to 9.6.6 and 9.2.7 databases to 9.6.24, and 9.6.24
databases to 13.8 using the old pg_dump binaries when it was impractical to
install the newer Postgresql in parallel with the old binaries.)
--
Angular momentum makes the world go 'round.
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-13 06:07 Tom Lane <tgl@sss.pgh.pa.us>
parent: Ron <ronljohnsonjr@gmail.com>
0 siblings, 1 reply; 31+ messages in thread
From: Tom Lane @ 2022-11-13 06:07 UTC (permalink / raw)
To: Ron <ronljohnsonjr@gmail.com>; +Cc: pgsql-general@lists.postgresql.org
Ron <ronljohnsonjr@gmail.com> writes:
> On 11/11/22 23:09, Adrian Klaver wrote:
>> 2) For your explanation above, pg_dump from 9.4(5432) to pg_restore
>> 12(5433) the issue would be ...\9.4\bin\pg_dump.exe of 9.4 and pg_restore
>> of said dump file to version 12. When moving up in version you need to use
>> the newer version of pg_dump(...\12\bin\pg_dump.exe) to dump the 9.4
>> instance and then the version 12 pg_restore to the 12 instance. Both
>> programs are backwards compatible, not forwards compatible.
> Unless there's some bug (you're running a /really/ old version of 9.4), you
> might be able to get away with using the 9.4 binary.
Yeah. The recommendation to use the later version's pg_dump for a
migration is in the nature of "this is best practice", not "this is
the only way that will work". The argument for it is that the older
pg_dump might have bugs that are fixed in the newer version. But
such bugs are rare, so usually it'll work fine to use the older one.
We do endeavor to make sure that older dump output will load into
newer versions, because in disaster-recovery scenarios an older
dump might be all you have.
regards, tom lane
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-13 16:46 Adrian Klaver <adrian.klaver@aklaver.com>
parent: Brad White <b55white@gmail.com>
1 sibling, 0 replies; 31+ messages in thread
From: Adrian Klaver @ 2022-11-13 16:46 UTC (permalink / raw)
To: Brad White <b55white@gmail.com>; +Cc: pgsql-general@lists.postgresql.org
On 11/12/22 18:18, Brad White wrote:
>
> > How where the restored copies made on the original cluster?
> I guess I'm not understanding the confusion here. They were restored
> with the same script but to a different DB name and with the 9.4
> executables.
> In fact, that was why the script was originally written, so we could
> restore and test the backups.
The confusion came from this:
"I only need the primary.
Not the half dozen restored copies."
I initially assumed, correctly as it turns out, that they all existed on
the production cluster and where duplicates.
Then you posted:
"Over time, we've restored multiple copies for testing and reproducing
various issues.
I'm only trying to set up replication one one of those copies. "
and showed a process where they being restored to other clusters.
At that point I was lost as to what copies meant and where they came from.
Not sure that this is actually pertinent to the problem at hand, I was
just trying to nail down the moving pieces.
>
> I've since hijacked it and used it to restore to other versions.
>
--
Adrian Klaver
adrian.klaver@aklaver.com
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-13 16:51 Adrian Klaver <adrian.klaver@aklaver.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 31+ messages in thread
From: Adrian Klaver @ 2022-11-13 16:51 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; Ron <ronljohnsonjr@gmail.com>; +Cc: pgsql-general@lists.postgresql.org
On 11/12/22 22:07, Tom Lane wrote:
> Ron <ronljohnsonjr@gmail.com> writes:
>> On 11/11/22 23:09, Adrian Klaver wrote:
>>> 2) For your explanation above, pg_dump from 9.4(5432) to pg_restore
>>> 12(5433) the issue would be ...\9.4\bin\pg_dump.exe of 9.4 and pg_restore
>>> of said dump file to version 12. When moving up in version you need to use
>>> the newer version of pg_dump(...\12\bin\pg_dump.exe) to dump the 9.4
>>> instance and then the version 12 pg_restore to the 12 instance. Both
>>> programs are backwards compatible, not forwards compatible.
>
>> Unless there's some bug (you're running a /really/ old version of 9.4), you
>> might be able to get away with using the 9.4 binary.
>
> Yeah. The recommendation to use the later version's pg_dump for a
> migration is in the nature of "this is best practice", not "this is
> the only way that will work". The argument for it is that the older
> pg_dump might have bugs that are fixed in the newer version. But
> such bugs are rare, so usually it'll work fine to use the older one.
> We do endeavor to make sure that older dump output will load into
> newer versions, because in disaster-recovery scenarios an older
> dump might be all you have.
I stand corrected.
I should have read the Notes here:
https://www.postgresql.org/docs/current/app-pgdump.html
>
> regards, tom lane
>
>
--
Adrian Klaver
adrian.klaver@aklaver.com
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-19 00:05 Brad White <b55white@gmail.com>
parent: Brad White <b55white@gmail.com>
1 sibling, 1 reply; 31+ messages in thread
From: Brad White @ 2022-11-19 00:05 UTC (permalink / raw)
To: ; +Cc: pgsql-general@lists.postgresql.org
tl;dr How do I turn up the logging so I can see what is failing?
In our quest to get replication working, we are upgrading from v9.4 to
v12.10.
Access365 via ODBC
Driver = "PostgreSQL Unicode" v13.02, Date 9/22/2021
In testing the app against v12, I find this issue:
On updating a record, I set values on several fields and call
recordSet.Update after each one.
After updating one particular field, calling Update gives
--> The Microsoft Access database engine stopped the process because you
and another user are attempting to change the same data at the same time.
Code in question:
rst!Update <-- success
rst!QtyDeliverable = rst!Quantity
rst.Update <-- fails here
The wisdom of the internet says that this is most likely with a BIT field
that has null that Access can't handle. But that isn't the case here. Both
are int4 fields and both have values before the update.
For context, this is after we've copied the order record. Then we copy this
Order Item record. Then we copy all the child records. Lastly, we are
updating a few fields in this Order Item record and the update fails.
This only fails against PostgreSQL 12.10, compiled by Visual C++ build
1914, 64-bit
Succeeds against PostgreSQL 9.4.1, compiled by Visual C++ build 1800, 64-bit
I don't see anything in the data\logs folder that looks relevant. Where
else should I look?
>
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-19 00:34 Adrian Klaver <adrian.klaver@aklaver.com>
parent: Brad White <b55white@gmail.com>
0 siblings, 1 reply; 31+ messages in thread
From: Adrian Klaver @ 2022-11-19 00:34 UTC (permalink / raw)
To: Brad White <b55white@gmail.com>; +Cc: pgsql-general@lists.postgresql.org
On 11/18/22 16:05, Brad White wrote:
> tl;dr How do I turn up the logging so I can see what is failing?
>
> In our quest to get replication working, we are upgrading from v9.4 to
> v12.10.
>
> Access365 via ODBC
> Driver = "PostgreSQL Unicode" v13.02, Date 9/22/2021
>
> In testing the app against v12, I find this issue:
>
> On updating a record, I set values on several fields and call
> recordSet.Update after each one.
> After updating one particular field, calling Update gives
>
> --> The Microsoft Access database engine stopped the process because you
> and another user are attempting to change the same data at the same time.
>
> Code in question:
> rst!Update <-- success
> rst!QtyDeliverable = rst!Quantity
> rst.Update <-- fails here
> The wisdom of the internet says that this is most likely with a BIT
> field that has null that Access can't handle. But that isn't the case
> here. Both are int4 fields and both have values before the update.
That wisdom:
https://odbc.postgresql.org/faq.html#6.4
also says
" PostgreSQL 7.2 and above can cause similar problems but for different
reasons:
Contributed by Sam Hokin (sam@ims.net)
The new PostgreSQL timestamp data type defaults to microsecond
precision. This means that timestamp values are stored like 2002-05-22
09:00:00.123456-05. However, Access does not support the extra
precision, so the value that Access uses is 2002-05-22 09:00:00-05. When
one tries to update a record, one gets the error message above because
the value that Access uses in its UPDATE query does not match the value
in the PostgreSQL table, similar to the NULL vs. empty string conflict
that is already reported in this FAQ entry. "
The above is the problem I usually ran into with Access and Postgres and
updating.
Is there a timestamp field in the record you are updating?
>
> For context, this is after we've copied the order record. Then we copy
> this Order Item record. Then we copy all the child records. Lastly, we
> are updating a few fields in this Order Item record and the update fails.
>
> This only fails against PostgreSQL 12.10, compiled by Visual C++ build
> 1914, 64-bit
> Succeeds against PostgreSQL 9.4.1, compiled by Visual C++ build 1800, 64-bit
>
> I don't see anything in the data\logs folder that looks relevant. Where
> else should I look?
>
--
Adrian Klaver
adrian.klaver@aklaver.com
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-22 20:53 Brad White <b55white@gmail.com>
parent: Adrian Klaver <adrian.klaver@aklaver.com>
0 siblings, 1 reply; 31+ messages in thread
From: Brad White @ 2022-11-22 20:53 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org
On 11/18/2022 6:34 PM, Adrian Klaver wrote:
> On 11/18/22 16:05, Brad White wrote:
>>
>> --> The Microsoft Access database engine stopped the process because
>> you and another user are attempting to change the same data at the
>> same time.
>>
>> Code in question:
>> rst!Update <-- success
>> rst!QtyDeliverable = rst!Quantity
>> rst.Update <-- fails here
>> The wisdom of the internet says that this is most likely with a BIT
>> field that has null that Access can't handle. But that isn't the case
>> here. Both are int4 fields and both have values before the update.
>
>
> The new PostgreSQL timestamp data type defaults to microsecond
> precision. This means that timestamp values are stored like 2002-05-22
> 09:00:00.123456-05. However, Access does not support the extra
> precision, so the value that Access uses is 2002-05-22 09:00:00-05.
> When one tries to update a record, one gets the error message above
> because the value that Access uses in its UPDATE query does not match
> the value in the PostgreSQL table, similar to the NULL vs. empty
> string conflict that is already reported in this FAQ entry. "
>
> The above is the problem I usually ran into with Access and Postgres
> and updating.
>
> Is there a timestamp field in the record you are updating?
>
UPDATE:
Yes, there are 5 timestamp fields.
It seems unlikely to be the culprit for 3 reasons.
1) It worked fine in v9.4
2) It worked the previous 4 times I saved that record in v12.
3) As the data came from Access, there is no data in any of the fields
in the last three decimal places.
ex. 45.234000
But as it is the best lead I have, and it could still be the culprit
until proven otherwise, I'm working to convert those 5 fields from
timestamp to timestamp(3).
Of course, PG doesn't allow to edit a table with dependent views.
Which means that I'm attempting to modify a script that will allow me to
save, drop, restore the views.
Of course, PG coerces all table and field names to lowercase unless quoted.
So I have to figure how to recognize all table names and add quotes.
This table is core to the app, so a LOT of the views reference it.
I may not be done anytime soon.
Have a good vacation!
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-22 21:19 Adrian Klaver <adrian.klaver@aklaver.com>
parent: Brad White <b55white@gmail.com>
0 siblings, 0 replies; 31+ messages in thread
From: Adrian Klaver @ 2022-11-22 21:19 UTC (permalink / raw)
To: Brad White <b55white@gmail.com>; pgsql-general@lists.postgresql.org
On 11/22/22 12:53, Brad White wrote:
>
> On 11/18/2022 6:34 PM, Adrian Klaver wrote:
>> On 11/18/22 16:05, Brad White wrote:
>>>
>>> --> The Microsoft Access database engine stopped the process because
>>> you and another user are attempting to change the same data at the
>>> same time.
>>>
>>> Code in question:
>>> rst!Update <-- success
>>> rst!QtyDeliverable = rst!Quantity
>>> rst.Update <-- fails here
>>> The wisdom of the internet says that this is most likely with a BIT
>>> field that has null that Access can't handle. But that isn't the case
>>> here. Both are int4 fields and both have values before the update.
>>
>>
>> The new PostgreSQL timestamp data type defaults to microsecond
>> precision. This means that timestamp values are stored like 2002-05-22
>> 09:00:00.123456-05. However, Access does not support the extra
>> precision, so the value that Access uses is 2002-05-22 09:00:00-05.
>> When one tries to update a record, one gets the error message above
>> because the value that Access uses in its UPDATE query does not match
>> the value in the PostgreSQL table, similar to the NULL vs. empty
>> string conflict that is already reported in this FAQ entry. "
>>
>> The above is the problem I usually ran into with Access and Postgres
>> and updating.
>>
>> Is there a timestamp field in the record you are updating?
>>
> UPDATE:
>
> Yes, there are 5 timestamp fields.
>
> It seems unlikely to be the culprit for 3 reasons.
>
> 1) It worked fine in v9.4
> 2) It worked the previous 4 times I saved that record in v12.
> 3) As the data came from Access, there is no data in any of the fields
> in the last three decimal places.
> ex. 45.234000
>
> But as it is the best lead I have, and it could still be the culprit
> until proven otherwise, I'm working to convert those 5 fields from
> timestamp to timestamp(3).
It is worse then that:
https://learn.microsoft.com/en-us/office/troubleshoot/access/store-calculate-compare-datetime-data
Valid time values range from .0 (00:00:00) to .99999 (23:59:59)
So no fractional seconds.
Before you do any of the below I would set up a test table with
timestamps and verify they are the issue.
>
> Of course, PG doesn't allow to edit a table with dependent views.
>
> Which means that I'm attempting to modify a script that will allow me to
> save, drop, restore the views.
>
> Of course, PG coerces all table and field names to lowercase unless quoted.
>
> So I have to figure how to recognize all table names and add quotes.
>
> This table is core to the app, so a LOT of the views reference it.
>
> I may not be done anytime soon.
>
> Have a good vacation!
>
>
>
--
Adrian Klaver
adrian.klaver@aklaver.com
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-29 00:02 Brad White <b55white@gmail.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 31+ messages in thread
From: Brad White @ 2022-11-29 00:02 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-general@lists.postgresql.org
Tom,
I tried to run initdb after re-installing pg 12
using postgresql-12.10-2-windows-x64.exe.
But the runas I'm using to execute it as pguser seems to be swallowing all
the output, so I can't see any errors.
I was able to run pg_checksums and get those enabled.
Is there anything else I want from initdb?
Or can I skip that?
On Fri, Nov 11, 2022 at 4:27 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Nonetheless,
> your path forward is clear: use pg_dump (or better pg_dumpall)
> and then load the output into a *freshly initdb'd v12 installation.*
> It'll be a bit slower than the pg_upgrade way, but it'll work.
>
> regards, tom lane
>
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-29 01:02 Tom Lane <tgl@sss.pgh.pa.us>
parent: Brad White <b55white@gmail.com>
0 siblings, 1 reply; 31+ messages in thread
From: Tom Lane @ 2022-11-29 01:02 UTC (permalink / raw)
To: Brad White <b55white@gmail.com>; +Cc: pgsql-general@lists.postgresql.org
Brad White <b55white@gmail.com> writes:
> I tried to run initdb after re-installing pg 12
> using postgresql-12.10-2-windows-x64.exe.
> But the runas I'm using to execute it as pguser seems to be swallowing all
> the output, so I can't see any errors.
> I was able to run pg_checksums and get those enabled.
> Is there anything else I want from initdb?
If you can connect to the new installation, then you're done with
that part, and can get on with the dump-and-restore part.
regards, tom lane
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: Upgrading to v12
@ 2022-11-29 02:23 Adrian Klaver <adrian.klaver@aklaver.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 31+ messages in thread
From: Adrian Klaver @ 2022-11-29 02:23 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; Brad White <b55white@gmail.com>; +Cc: pgsql-general@lists.postgresql.org
On 11/28/22 17:02, Tom Lane wrote:
> Brad White <b55white@gmail.com> writes:
>> I tried to run initdb after re-installing pg 12
>> using postgresql-12.10-2-windows-x64.exe.
>> But the runas I'm using to execute it as pguser seems to be swallowing all
>> the output, so I can't see any errors.
>> I was able to run pg_checksums and get those enabled.
>> Is there anything else I want from initdb?
>
> If you can connect to the new installation, then you're done with
> that part, and can get on with the dump-and-restore part.
Yeah this is coming from this SO question:
https://stackoverflow.com/questions/74607304/what-results-should-i-see-from-running-initdb#comment13...
Brad was double clutching on the initdb.
>
> regards, tom lane
>
>
--
Adrian Klaver
adrian.klaver@aklaver.com
^ permalink raw reply [nested|flat] 31+ messages in thread
end of thread, other threads:[~2022-11-29 02:23 UTC | newest]
Thread overview: 31+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-11-11 20:43 Upgrading to v12 Brad White <b55white@gmail.com>
2022-11-11 21:02 ` Adrian Klaver <adrian.klaver@aklaver.com>
2022-11-11 21:05 ` Brad White <b55white@gmail.com>
2022-11-11 21:11 ` Brad White <b55white@gmail.com>
2022-11-11 21:16 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-11-11 21:17 ` Adrian Klaver <adrian.klaver@aklaver.com>
2022-11-11 21:42 ` Brad White <b55white@gmail.com>
2022-11-12 02:41 ` Brad White <b55white@gmail.com>
2022-11-12 02:43 ` Brad White <b55white@gmail.com>
2022-11-12 03:57 ` Adrian Klaver <adrian.klaver@aklaver.com>
2022-11-12 04:59 ` Brad White <b55white@gmail.com>
2022-11-12 05:09 ` Adrian Klaver <adrian.klaver@aklaver.com>
2022-11-13 02:06 ` Brad White <b55white@gmail.com>
2022-11-13 02:18 ` Brad White <b55white@gmail.com>
2022-11-13 16:46 ` Adrian Klaver <adrian.klaver@aklaver.com>
2022-11-19 00:05 ` Brad White <b55white@gmail.com>
2022-11-19 00:34 ` Adrian Klaver <adrian.klaver@aklaver.com>
2022-11-22 20:53 ` Brad White <b55white@gmail.com>
2022-11-22 21:19 ` Adrian Klaver <adrian.klaver@aklaver.com>
2022-11-13 05:30 ` Ron <ronljohnsonjr@gmail.com>
2022-11-13 06:07 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-11-13 16:51 ` Adrian Klaver <adrian.klaver@aklaver.com>
2022-11-12 08:44 ` Ron <ronljohnsonjr@gmail.com>
2022-11-13 02:07 ` Brad White <b55white@gmail.com>
2022-11-13 02:12 ` Brad White <b55white@gmail.com>
2022-11-11 22:06 ` Brad White <b55white@gmail.com>
2022-11-11 22:27 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-11-29 00:02 ` Brad White <b55white@gmail.com>
2022-11-29 01:02 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-11-29 02:23 ` Adrian Klaver <adrian.klaver@aklaver.com>
2022-11-12 00:11 ` Adrian Klaver <adrian.klaver@aklaver.com>
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