Andres Freund <and...@anarazel.de> writes: > It's not quite there yet, unfortunately. At the moment > pg_atomic_write_u32() is used for local buffers - and we explicitly > don't want that to be locking for temp buffers > (c.f. 6b93fcd149329d4ee7319561b30fc15a573c6307).
Hm. > Don't really have a great idea about addressing this, besides either > just living with the lock for temp buffers on fallback platforms (which > don't have much of a practical relevance), or introduce > pg_atomic_unlocked_write_u32() or something. Neither seems great. Maybe we could hack it with some macro magic that would cause pg_atomic_write_u32() to be expanded into a simple assignment in localbuf.c only? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers