Home

clients - Search results

List

Post date

Sort by

client backend (PID 3504475) was terminated by signal 11: Segmentation fault 2025-04-24 05:29:27.112 CEST

client backend][0/2:0] DEBUG: waiting for self with 0 pending 2025-04-08 01:41:54.674 UTC [4013251][client

client backend (PID 3320979) was terminated by signal 11: Segmentation fault 2025-04-15 19:21:30.675 EEST

client of the bufmgr subsystem, e.g. read_stream.c, does accesses only after that. The client

client requests. - If the worker relies on the AIO-subsystem-owned pin and does neither

client requests. This example uses local buffers. Storage for those comes from MemoryContextAlloc() in GetLocalBufferStorage

client backend][3/6:0] LOG: short read injection point called, is enabled: 0 ==2486740== VALGRINDERROR

client twice than to the server log. I'm happy to change it to LOG if you prefer

client message - client already gone The choice between LOG and LOG_SERVER_ONLY doesn't matter

client as a WARNING explicitly when the IO's results are processed I actually chose

client connection. I think that part is fine, but... I thought it'd be better

client in a *normal* situation. I'm thinking of something like an insert extending a relation

client gets an unexpected WARNING. The process getting the WARNING may not even have zero