From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Processes and caches in postgresql |
Date: | 2016-05-02 12:36:14 |
Message-ID: | CA+TgmoaCgieM6wcN=xhKnirpskJ=jrN9nf2xeoWOo8i04Yxk+g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Apr 27, 2016 at 7:07 AM, Anastasia Lubennikova
<a(dot)lubennikova(at)postgrespro(dot)ru> wrote:
> Hi, hackers.
> There's a couple of questions about processes.
>
> I found EXEC_BACKEND flag, while reading the code.
> As I understood, it exists because we have to emulate fork() on WIN32.
> And also it allows to debug the same behavior on Linux.
> Is it right? Are there any other use cases?
Right. Or, more precisely, we can't really emulate fork(), so we have
to make due with what's available on Windows, which is basically
exec().
> Another question is about "--fork" argument (see code below).
> I didn't find it in documentation, so I'm a bit confused.
> I wonder if it exists only for internal purposes?
Correct. Just for internal purposes only - definitely not intended
for users to invoke directly.
> And the last, but not least. Do we have any
> presentations/articles/READMEs/whatever
> about caches (src/backend/utils/cache/*) in postgresql?
> I found nothing, besides comments in the code.
Nothing specific comes to mind.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2016-05-02 12:45:27 | Re: what does function EmitWarningsOnPlaceholders? |
Previous Message | Craig Ringer | 2016-05-02 11:54:37 | Re: what does function EmitWarningsOnPlaceholders? |