|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|Cc:||Noah Misch <noah(at)leadboat(dot)com>|
|Subject:||Unexpected "shared memory block is still in use"|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Just now, while running a parallel check-world on HEAD according to the
same script I've been using for quite some time, one of the TAP tests
died during initdb:
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default timezone ... America/New_York
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... 2019-05-08 13:59:19.963 EDT  FATAL: pre-existing shared memory block (key 5440004, ID 1734475802) is still in use
2019-05-08 13:59:19.963 EDT  HINT: Terminate any old server processes associated with data directory "/home/postgres/pgsql/src/test/subscription/tmp_check/t_004_sync_publisher_data/pgdata".
child process exited with exit code 1
initdb: removing data directory "/home/postgres/pgsql/src/test/subscription/tmp_check/t_004_sync_publisher_data/pgdata"
Bail out! system initdb failed
I have never seen this happen before in the TAP tests.
I think the odds are very high that this implies something wrong with
My immediate guess after eyeballing that patch quickly is that it was
not a good idea to redefine the rules used by bootstrap/standalone
backends. In particular, it seems somewhat plausible that the bootstrap
process hadn't yet completely died when the standalone backend for the
post-bootstrap phase came along and decided there was a conflict (which
it never would have before).
regards, tom lane
|Next Message||Andrew Dunstan||2019-05-08 18:56:25||Re: Statistical aggregate functions are not working with PARTIAL aggregation|
|Previous Message||Andres Freund||2019-05-08 18:31:14||Re: [HACKERS] Detrimental performance impact of ringbuffers on performance|