Hi, low-memory testing with REL_10_STABLE at 1f19550a87 produced the following PANIC:
stuck spinlock detected at pg_stat_get_wal_receiver, walreceiver.c:1397
I was about to wrap the pstrdup()s with a PG_TRY block, but I can't find
a spinlock being released in a PG_CATCH block anywhere, so maybe that's
a bad idea?
regards,
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
