Re: [HACKERS] [ADMIN] postgresql in FreeBSD jails: proposal

2008-01-17 Thread Alvaro Herrera
Cc: [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@postgresql.org.pgsql-chat@post Hey, this is exactly the sort of weird Cc: line I saw in the recent spam surge. Since I suspect you are using the news server to post, I suggest you take a long and careful look at the

Re: [HACKERS] [ADMIN] postgresql in FreeBSD jails: proposal

2008-01-17 Thread Dave Page
On 17/01/2008, Alvaro Herrera [EMAIL PROTECTED] wrote: Cc: [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@postgresql.org.pgsql-chat@post Hey, this is exactly the sort of weird Cc: line I saw in the recent spam surge. Since I suspect you are using the news server to

Re: [HACKERS] [ADMIN] postgresql in FreeBSD jails: proposal

2008-01-17 Thread Stephen Frost
* Tom Lane ([EMAIL PROTECTED]) wrote: Marc G. Fournier [EMAIL PROTECTED] writes: Easiest fix: change the UID of the user running the postmaster (ie. pgsql) so that each runs as a distinct UID (instead of distinct PGPORT) ... been doing this since moving to FreeBSD 6.x ... no patches

Re: [HACKERS] [ADMIN] postgresql in FreeBSD jails: proposal

2008-01-17 Thread Marc G. Fournier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Thursday, January 17, 2008 13:58:36 + Dave Page [EMAIL PROTECTED] wrote: On 17/01/2008, Alvaro Herrera [EMAIL PROTECTED] wrote: Cc: [EMAIL PROTECTED]@postgresql.org.pgadmin-suppo [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL

Re: [HACKERS] [ADMIN] postgresql in FreeBSD jails: proposal

2008-01-17 Thread Tom Lane
Mischa Sandberg [EMAIL PROTECTED] writes: If anyone is interested in creating hung backends, you can create a named pipe, and tell the server to COPY from it. That won't create a problematic situation though, until/unless you SIGQUIT the parent postmaster. Personally I think of this as what

Re: [HACKERS] [ADMIN] postgresql in FreeBSD jails: proposal

2008-01-17 Thread Tom Lane
Mischa Sandberg [EMAIL PROTECTED] writes: I'm going to skip the kill(1,0) test and depend on nattch only, with a function that PGSharedMemoryIsInUse() can also use. (For a healthy server, nattch is never less than 2, right?) Oh, forgot to mention: healthy servers are not the point here. You

Re: [HACKERS] [ADMIN] postgresql in FreeBSD jails: proposal

2008-01-17 Thread Mischa Sandberg
Quoting Stephen Frost [EMAIL PROTECTED]: * Tom Lane ([EMAIL PROTECTED]) wrote: Marc G. Fournier [EMAIL PROTECTED] writes: Easiest fix: change the UID of the user running the postmaster (ie. pgsql) so that each runs as a distinct UID (instead of distinct PGPORT) ... been doing this

Re: [HACKERS] [ADMIN] postgresql in FreeBSD jails: proposal

2008-01-17 Thread Mischa Sandberg
Quoting Tom Lane [EMAIL PROTECTED]: Mischa Sandberg [EMAIL PROTECTED] writes: I'm going to skip the kill(1,0) test and depend on nattch only, with a function that PGSharedMemoryIsInUse() can also use. (For a healthy server, nattch is never less than 2, right?) Oh, forgot to mention:

Re: [HACKERS] [ADMIN] postgresql in FreeBSD jails: proposal

2008-01-16 Thread Marc G. Fournier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Thursday, January 17, 2008 01:12:54 -0500 Tom Lane [EMAIL PROTECTED] wrote: Marc G. Fournier [EMAIL PROTECTED] writes: [EMAIL PROTECTED] (Mischa Sandberg) writes: Unfortunately, with multiple jails running PG servers and (due to app

Re: [HACKERS] [ADMIN] postgresql in FreeBSD jails: proposal

2008-01-16 Thread Tom Lane
Marc G. Fournier [EMAIL PROTECTED] writes: [EMAIL PROTECTED] (Mischa Sandberg) writes: Unfortunately, with multiple jails running PG servers and (due to app limitations) all servers having same PGPORT, you get the situation that when jail#2 (,jail#3,...) server comes up, it: - detects that