> In a standalone backend, I think there are only 3 ways to get to
> normal shutdown:
>* SIGTERM
>* SIGQUIT
> * EOF on stdin
I debugged a bit more and I see that getc() returns with -1 in
interactive_getc() which is interpreted as EOF:
c = getc(stdin);
I see that errno ==
Stanislav Bashkyrtsev writes:
>> Why do you think postgres quits?
> The process was running and then it stopped. And in the console I see:
> 2022-01-03 23:23:29.495 MSK [76717] LOG: checkpoint starting: shutdown
> immediate
In a standalone backend, I think there are only 3 ways to get to
> Why do you think postgres quits?
The process was running and then it stopped. And in the console I see:
2022-01-03 23:23:29.495 MSK [76717] LOG: checkpoint starting: shutdown
immediate
2022-01-03 23:23:29.498 MSK [76717] LOG: checkpoint complete: wrote 3
buffers (0.0%); 0 WAL file(s) added, 0
Tomas Vondra writes:
> On 1/3/22 16:54, Stanislav Bashkyrtsev wrote:
>> - If I put a breakpoint before I start the process then everything works
>> fine
>> - But if I put/remove a breakpoint after it's fully initialized - the
>> process just stops
> Why do you think postgres quits? AFAIK CLion
On 1/3/22 16:54, Stanislav Bashkyrtsev wrote:
I tried debugging PostgreSQL to better understand how it works. It
worked fine a day ago, but for some reason I have issues with debugging now:
- If I put a breakpoint before I start the process then everything works
fine
- But if I put/remove a
I tried debugging PostgreSQL to better understand how it works. It worked
fine a day ago, but for some reason I have issues with debugging now:
- If I put a breakpoint before I start the process then everything works
fine
- But if I put/remove a breakpoint after it's fully initialized - the
