Re: stopping processes, preventing connections - Mailing list pgsql-general

From Scott Marlowe
Subject Re: stopping processes, preventing connections
Date
Msg-id dcc563d11003201612h13378a7ap5d1e5334fde010c8@mail.gmail.com
Whole thread Raw
In response to Re: stopping processes, preventing connections  (Herouth Maoz <herouth@unicell.co.il>)
Responses Re: stopping processes, preventing connections  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-general
On Sat, Mar 20, 2010 at 3:57 PM, Herouth Maoz <herouth@unicell.co.il> wrote:
>
>
> The problem is not so much danger in upgrading, but the fact that doing so
> without using the system's usual security/bugfix update path means
> non-standard work for the sysadmin, meaning he has to upgrade every package
> on the system using a different upgrade method, being notified about it from
> a different source, and needing to check each one in different conditions,
> which makes his work impossible. So the policy so far has been "Use the
> packages available through debian". So I'll need to check if there is an
> upgrade available through that path - and the question is whether it's
> worthwhile (i.e. whether the bug in question has indeed been fixed).

I'm certain debian keeps the pgsql packages up to date within a few
days or at most weeks of their release .

pgsql-general by date:

Previous
From: Adam Seering
Date:
Subject: Restrict allowed database names?
Next
From: Jay
Date:
Subject: Re: Help me with this tricky join