Re: [HACKERS] Installation procedure. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Installation procedure.
Date
Msg-id 151.933570583@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Installation procedure.  ("J. Michael Roberts" <mirobert@cs.indiana.edu>)
List pgsql-hackers
"J. Michael Roberts" <mirobert@cs.indiana.edu> writes:
> Now to figure out how to get the changes to you
> guys....  Is the procedure simply to diff it and email it to somebody, or
> what?

Standard operating procedure is to make a patch-compatible diff
(I think -c format is preferred) and post it to the pgsql-patches
mailing list.  If you have a real good idea which core member is
probably going to apply the patch you could send it just to that
person, but it's more courteous to put it on the public mailing list.

> As to whether MAXBACKENDS should be changed -- I have no idea what impact
> that would actually have.  What *is* a backend, precisely?  In Illustra,
> anyway, each active query starts a new process while it's working -- is
> that a backend?

No.  There's one backend process per client connection; it lives till
the client disconnects, and handles all queries that come through that
connection.  So MAXBACKENDS really means "how many simultaneous
clients am I expecting"?
        regards, tom lane


pgsql-hackers by date:

Previous
From: "J. Michael Roberts"
Date:
Subject: Re: [HACKERS] Installation procedure.
Next
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] Installation procedure.