Home > mailing lists

Thread: [BUGS] Bug 14592

[BUGS] Bug 14592

From

Matthew Zinicola

Date:

03 May 2017, 23:59:32

Any update on this issue? It is a server crash that I continue to experience daily with 9.6.2.

If a fix isn't forthcoming, can I safely downgrade to 9.5.6?

Thanks,

-Matt

Re: [BUGS] Bug 14592

From

Andres Freund

Date:

04 May 2017, 00:19:46

On 2017-05-03 13:59:32 -0400, Matthew Zinicola wrote:
> Any update on this issue?  It is a server crash that I continue to
> experience daily with 9.6.2.

I see no bugreport with that number.  Could you either provide a link or
a new description of the issue?


> If a fix isn't forthcoming, can I safely downgrade to 9.5.6?

Not without a dump & restore, no.

Greetings,

Andres Freund


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] Bug 14592

From

Alvaro Herrera

Date:

04 May 2017, 00:20:41

Matthew Zinicola wrote:
> Any update on this issue?  It is a server crash that I continue to
> experience daily with 9.6.2.

Please resubmit.  There is no such report in the archives.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] Bug 14592

From

"David G. Johnston"

Date:

04 May 2017, 00:20:53

On Wed, May 3, 2017 at 10:59 AM, Matthew Zinicola <mattzinicola@gmail.com> wrote:

Any update on this issue? It is a server crash that I continue to experience daily with 9.6.2.

If a fix isn't forthcoming, can I safely downgrade to 9.5.6?

I see initial reports for bugs 14591 and 14593 - but nothing for 14592...which should have been issued roughly March 16th.

https://www.postgresql.org/list/pgsql-bugs/2017-03/

I'm adding -www since a form submission the results in a bug number should appear in our archives.

You might want to re-post the report here in the meantime.

David J.

Re: [BUGS] Bug 14592

From

Matthew Zinicola

Date:

04 May 2017, 00:27:17

Here is the information I originally provided:

Bug reference: 14592
Logged by: Matt Zinicola
Email address: mattzinicola@gmail.com
PostgreSQL version: 9.6.2
Operating system: Linux 4.9.13-201.fc25.x86_64
Description:

Log output:

2017-03-17 12:32:20.311 UTCFATAL: XX000: semctl(16187416, 0, SETVAL, 0)
failed: Invalid argument
2017-03-17 12:32:20.311 UTCLOCATION: IpcSemaphoreInitialize,
pg_sema.c:150
2017-03-17 12:32:20.312 UTCLOG: 00000: server process (PID 9720) exited
with exit code 1
2017-03-17 12:32:20.312 UTCLOCATION: LogChildExit, postmaster.c:3481
2017-03-17 12:32:20.312 UTCLOG: 00000: terminating any other active server
processes
2017-03-17 12:32:20.312 UTCLOCATION: HandleChildCrash, postmaster.c:3223
2017-03-17 12:32:20.312 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.312 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.312 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.312 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.312 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.312 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.312 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.312 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.312 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.312 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.312 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.312 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.312 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.312 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.312 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.312 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.312 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.312 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.312 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.312 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.313 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.313 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.313 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.313 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.313 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.313 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.313 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.313 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.314 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.314 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.314 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.314 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.314 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.314 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.314 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.314 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.315 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.315 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.315 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.315 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.316 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.316 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.316 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.316 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.317 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.317 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.317 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.317 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.317 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.317 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.317 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.317 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.318 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.318 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.318 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.318 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.319 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.319 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.319 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.319 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.319 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.319 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.319 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.319 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.319 UTCWARNING: 57P02: terminating connection because
of crash of another server process
2017-03-17 12:32:20.319 UTCDETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2017-03-17 12:32:20.319 UTCHINT: In a moment you should be able to
reconnect to the database and repeat your command.
2017-03-17 12:32:20.319 UTCLOCATION: quickdie, postgres.c:2601
2017-03-17 12:32:20.320 UTCLOG: 00000: all server processes terminated;
reinitializing
2017-03-17 12:32:20.320 UTCLOCATION: PostmasterStateMachine,
postmaster.c:3747
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15400960, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15433729, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15466498, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15499267, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15532036, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15564805, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15597574, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15630343, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15663112, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15695881, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15728650, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15761419, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15794188, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15826957, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15859726, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15892495, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15925264, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15958033, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(15990802, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(16023571, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(16056340, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(16089109, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(16121878, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(16154647, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(16187416, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.321 UTCLOG: 00000: semctl(16220185, 0, IPC_RMID, ...)
failed: Invalid argument
2017-03-17 12:32:20.321 UTCLOCATION: IpcSemaphoreKill, pg_sema.c:165
2017-03-17 12:32:20.358 UTCLOG: 00000: database system was interrupted;
last known up at 2017-03-17 12:30:44 UTC
2017-03-17 12:32:20.358 UTCLOCATION: StartupXLOG, xlog.c:6019
2017-03-17 12:32:20.515 UTCLOG: 00000: database system was not properly
shut down; automatic recovery in progress
2017-03-17 12:32:20.515 UTCLOCATION: StartupXLOG, xlog.c:6499
2017-03-17 12:32:20.521 UTCLOG: 00000: redo starts at E/A2C34F58
2017-03-17 12:32:20.521 UTCLOCATION: StartupXLOG, xlog.c:6754
2017-03-17 12:32:20.575 UTCLOG: 00000: invalid record length at E/A30CA380:
wanted 24, got 0
2017-03-17 12:32:20.575 UTCLOCATION: ReadRecord, xlog.c:4018
2017-03-17 12:32:20.575 UTCLOG: 00000: redo done at E/A30CA358
2017-03-17 12:32:20.575 UTCLOCATION: StartupXLOG, xlog.c:7017
2017-03-17 12:32:20.575 UTCLOG: 00000: last completed transaction was at
log time 2017-03-17 12:32:16.508864+00
2017-03-17 12:32:20.575 UTCLOCATION: StartupXLOG, xlog.c:7022
2017-03-17 12:32:21.039 UTCLOG: 00000: MultiXact member wraparound
protections are now enabled
2017-03-17 12:32:21.039 UTCLOCATION: SetOffsetVacuumLimit,
multixact.c:2624
2017-03-17 12:32:21.040 UTCLOG: 00000: database system is ready to accept
connections
2017-03-17 12:32:21.040 UTCLOCATION: reaper, postmaster.c:2816
2017-03-17 12:32:21.041 UTCLOG: 00000: autovacuum launcher started
2017-03-17 12:32:21.041 UTCLOCATION: AutoVacLauncherMain, autovacuum.c:416

On Wed, May 3, 2017 at 2:20 PM, David G. Johnston <david.g.johnston@gmail.com> wrote:

On Wed, May 3, 2017 at 10:59 AM, Matthew Zinicola <mattzinicola@gmail.com> wrote:
Any update on this issue? It is a server crash that I continue to experience daily with 9.6.2.

If a fix isn't forthcoming, can I safely downgrade to 9.5.6?

I see initial reports for bugs 14591 and 14593 - but nothing for 14592...which should have been issued roughly March 16th.

https://www.postgresql.org/list/pgsql-bugs/2017-03/

I'm adding -www since a form submission the results in a bug number should appear in our archives.

You might want to re-post the report here in the meantime.

David J.

Re: [BUGS] Bug 14592

From

Matthew Zinicola

Date:

04 May 2017, 00:28:33

I was concerned that a dump and restore might cause an issue as well, but if that would be safe i was contemplating that route.

On Wed, May 3, 2017 at 2:19 PM, Andres Freund <andres@anarazel.de> wrote:

On 2017-05-03 13:59:32 -0400, Matthew Zinicola wrote:
> Any update on this issue? It is a server crash that I continue to
> experience daily with 9.6.2.

I see no bugreport with that number. Could you either provide a link or
a new description of the issue?

> If a fix isn't forthcoming, can I safely downgrade to 9.5.6?

Not without a dump & restore, no.

Greetings,

Andres Freund

Re: [BUGS] Bug 14592

From

Alvaro Herrera

Date:

04 May 2017, 00:42:44

Matthew Zinicola wrote:
> Here is the information I originally provided:
> 
> Bug reference:      14592
> Logged by:          Matt Zinicola
> Email address:      mattzinicola@gmail.com
> PostgreSQL version: 9.6.2
> Operating system:   Linux 4.9.13-201.fc25.x86_64
> Description:
> 
> Log output:
> 
> 2017-03-17 12:32:20.311 UTCFATAL:  XX000: semctl(16187416, 0, SETVAL, 0)
> failed: Invalid argument

Hmm, this looks familiar:
https://www.postgresql.org/message-id/30943.1481076987%40sss.pgh.pa.us

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Re: [BUGS] Bug 14592

From

Magnus Hagander

Date:

04 May 2017, 00:44:06

On Wed, May 3, 2017 at 8:20 PM, David G. Johnston <david.g.johnston@gmail.com> wrote:

On Wed, May 3, 2017 at 10:59 AM, Matthew Zinicola <mattzinicola@gmail.com> wrote:
Any update on this issue? It is a server crash that I continue to experience daily with 9.6.2.

If a fix isn't forthcoming, can I safely downgrade to 9.5.6?

I see initial reports for bugs 14591 and 14593 - but nothing for 14592...which should have been issued roughly March 16th.

https://www.postgresql.org/list/pgsql-bugs/2017-03/

I'm adding -www since a form submission the results in a bug number should appear in our archives.

Bug reports go through the general mailinglist moderation steps. My guess is that either the bug report was accidentally rejected by moderators, or it was missed for long enough that it expired (unless it's still sitting in the queue, but that seems unlikely given the approximate dates).

Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/

Re: [BUGS] Bug 14592

From

Alvaro Herrera

Date:

04 May 2017, 00:49:49

Magnus Hagander wrote:

> Bug reports go through the general mailinglist moderation steps. My guess
> is that either the bug report was accidentally rejected by moderators, or
> it was missed for long enough that it expired (unless it's still sitting in
> the queue, but that seems unlikely given the approximate dates).

I checked the queue, and it expired long ago.  These requests only live
for a week.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Re: [BUGS] Bug 14592

From

Matthew Zinicola

Date:

04 May 2017, 01:02:07

Thanks, gentlemen. I've consulted the link about this and made one of the two changes and I'm testing. I appreciate it, as I've never experienced anything this (relative to postgres or systemd).. and I've been using postgres for longer than I'd like to admit! :)

-Matt

On Wed, May 3, 2017 at 2:49 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:

Magnus Hagander wrote:

> Bug reports go through the general mailinglist moderation steps. My guess
> is that either the bug report was accidentally rejected by moderators, or
> it was missed for long enough that it expired (unless it's still sitting in
> the queue, but that seems unlikely given the approximate dates).

I checked the queue, and it expired long ago. These requests only live
for a week.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Re: [pgsql-www] [BUGS] Bug 14592

From

Tom Lane

Date:

04 May 2017, 02:50:20

Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> Matthew Zinicola wrote:
>> 2017-03-17 12:32:20.311 UTCFATAL:  XX000: semctl(16187416, 0, SETVAL, 0)
>> failed: Invalid argument

> Hmm, this looks familiar:
> https://www.postgresql.org/message-id/30943.1481076987%40sss.pgh.pa.us

If it is the systemd-kills-your-semaphores problem, downgrading to 9.5
would not fix it.  The thing to be looking at is what else you changed
when moving to 9.6.  Maybe you are using a different packaging, or
different way of starting the server?
        regards, tom lane


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [pgsql-www] [BUGS] Bug 14592

From

Tom Lane

Date:

04 May 2017, 05:11:34

Matt Zinicola <mattzinicola@gmail.com> writes:
> I changed hardware and OS, too, moving from older hardware and (pre-systemd) Fedora 14 to Fedora 25.  I used that as
anopportunity to upgrade Postgres from 9.5.5 to 9.6.2. 

Ah.  So the problem came in with systemd.  See the already-cited
references for ways to prevent systemd from zapping you.

We have a better answer lined up for PG10 --- viz, don't use
SysV-style semaphores anymore --- but nobody wanted to risk
back-patching such a major change into stable branches.
        regards, tom lane


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs