BUG #16426: In active/hot standby mode, create database and drop template databases cause standby restart failed

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: bchen90(at)163(dot)com
Subject: BUG #16426: In active/hot standby mode, create database and drop template databases cause standby restart failed
Date: 2020-05-09 12:44:53
Message-ID: 16426-8150eafd94d1ba37@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16426
Logged by: BoChen
Email address: bchen90(at)163(dot)com
PostgreSQL version: 11.5
Operating system: SUSE Linux Enterprise Server 11 (x86_64)
Description:

In active/hot standby mod, doing likes the following:

1) using createdb to create a database 'test'
2) drop template0 and template1 database
3) using 'pt_ctl stop -mi' to stop the standby db
4) restart the standby db, start failed

Run logs show that the failed reason is redoing xlog of create database
while the template database has been droped. After reading postgresql source
code. I suspect that the problem is related to not updating pg_contral file
when the standby redoing Xlog of checkpoint.

Is this a Bug?

standby db run log:

startup 36289 2020-05-09 19:55:18.666 CGPCONTEXT: WAL redo at 0/5000CE8 for
Standby/RUNNING_XACTS: nextXid 708 latestCompletedXid 706 oldestRunningXid
707; 1 xacts: 707
startup 36289 2020-05-09 19:55:18.666 CGPDEBUG: prune KnownAssignedXids to
707 procarray.c (3765 KnownAssignedXidsRemovePreceding)
startup 36289 2020-05-09 19:55:18.666 CGPCONTEXT: WAL redo at 0/5000D88 for
Standby/RUNNING_XACTS: nextXid 708 latestCompletedXid 706 oldestRunningXid
707; 1 xacts: 707
startup 36289 2020-05-09 19:55:18.666 CGPDEBUG: record known xact 707
latestObservedXid 707 procarray.c (3205 RecordKnownAssignedTransactionIds)
startup 36289 2020-05-09 19:55:18.666 CGPCONTEXT: WAL redo at 0/5000DC0 for
Database/CREATE: copy dir 1/1663 to 16384/1663
startup 36289 2020-05-09 19:55:18.673 CGPFATAL: could not open directory
"base/1": No such file or directory fd.c (2714 ReadDirExtended)
startup 36289 2020-05-09 19:55:18.673 CGPCONTEXT: WAL redo at 0/5000DC0 for
Database/CREATE: copy dir 1/1663 to 16384/1663
startup 36289 2020-05-09 19:55:18.673 CGPDEBUG: shmem_exit(1): 1
before_shmem_exit callbacks to make ipc.c (246 shmem_exit)
startup 36289 2020-05-09 19:55:18.673 CGPDEBUG: shmem_exit(1): 5
on_shmem_exit callbacks to make ipc.c (279 shmem_exit)
startup 36289 2020-05-09 19:55:18.673 CGPDEBUG: proc_exit(1): 2 callbacks
to make ipc.c (206 proc_exit_prepare)
startup 36289 2020-05-09 19:55:18.673 CGPDEBUG: exit(1) ipc.c (159
proc_exit)
postmaster 36286 2020-05-09 19:55:18.777 CGPLOG: timezone has changed,
checked for 1 times. pgtz_hw.c (93 NeedUpdateTz)
postmaster 36286 2020-05-09 19:55:18.777 CGPLOG: update last timezone
change time to (1589011223), check times=1. pgtz_hw.c (197 IsSameTimezone)
postmaster 36286 2020-05-09 11:55:18.777 UTCLOG: tz change, now
g_LogTimeMem is 1, g_LogTimeLocal is 1, flag is 0. pgtz_hw.c (276
AdjustLogTzChgTimesByPostmaster)
postmaster 36286 2020-05-09 11:55:18.777 UTCDEBUG: reaping dead processes
postmaster.c (2907 reaper)
postmaster 36286 2020-05-09 11:55:18.777 UTCDEBUG: server process (PID
36287) exited with exit code 0 postmaster.c (3697 LogChildExit)
postmaster 36286 2020-05-09 11:55:18.777 UTCLOG: startup process (PID
36289) exited with exit code 1 postmaster.c (3697 LogChildExit)

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Euler Taveira 2020-05-09 14:24:51 Re: BUG #16426: In active/hot standby mode, create database and drop template databases cause standby restart failed
Previous Message Fujii Masao 2020-05-09 03:26:22 Re: Back-patch is necessary? Re: Don't try fetching future segment of a TLI.