From: | Greg Nancarrow <gregn4422(at)gmail(dot)com> |
---|---|
To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints |
Date: | 2021-12-01 06:37:45 |
Message-ID: | CAJcOf-e-DiAERJWD6-9nKjqARttJZzppNFtUNrMZ7qe9JNO-mg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Nov 25, 2021 at 10:17 PM Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
>
> Thanks for the review and many valuable comments, I have fixed all of
> them except this comment (/* If we got a cancel signal during the copy
> of the data, quit */) because this looks fine to me. 0007, I have
> dropped from the patchset for now. I have also included fixes for
> comments given by John.
>
I found the following issue with the patches applied:
A server crash occurs after the following sequence of commands:
create tablespace tbsp1 location '<directory>/tbsp1';
create tablespace tbsp2 location '<directory>/tbsp2';
create database test1 tablespace tbsp1;
create database test2 template test1 tablespace tbsp2;
alter database test2 set tablespace tbsp1;
checkpoint;
The following type of message is seen in the server log:
2021-12-01 16:48:26.623 AEDT [67423] PANIC: could not fsync file
"pg_tblspc/16385/PG_15_202111301/16387/3394": No such file or
directory
2021-12-01 16:48:27.228 AEDT [67422] LOG: checkpointer process (PID
67423) was terminated by signal 6: Aborted
2021-12-01 16:48:27.228 AEDT [67422] LOG: terminating any other
active server processes
2021-12-01 16:48:27.233 AEDT [67422] LOG: all server processes
terminated; reinitializing
Also (prior to running the checkpoint command above) I've seen errors
like the following when running pg_dumpall:
pg_dump: error: connection to server on socket "/tmp/.s.PGSQL.5432"
failed: PANIC: could not open critical system index 2662
pg_dumpall: error: pg_dump failed on database "test2", exiting
Hopefully the above example will help in tracking down the cause.
Regards,
Greg Nancarrow
Fujitsu Australia
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2021-12-01 06:40:39 | Re: pg_get_publication_tables() output duplicate relid |
Previous Message | houzj.fnst@fujitsu.com | 2021-12-01 06:27:33 | RE: Skipping logical replication transactions on subscriber side |