Hi Steve,
Did you check if your OS allows you to limit memory usage per user /
process basis?
Did you either profiled or debugged it to see what is going on?
When memory consumption grows , Doesn't ever swap out?
Thanks,
A.A.
On Tue, Apr 8, 2014 at 10:48 AM, Steve Kehlet wrote:
> I'm runnin
Hi Ken,
With that level of dinamism of application servers where there is no way to
keep consistency among them , as you say concurrency must be turned into a
single thread to make sure schema migration will not be locked up by
application threads .
Have you though about constraining connections
Hi Ken,
Do you really need to allow web server connections to the database during a
schema migration ? Why not locking them up either with pg_hba.cong or a
firewal rule or symply shut it off temporarily ?
Cheers,
A.A.
On Fri, Mar 21, 2014 at 10:46 AM, Ken Barber wrote:
> Hi there,
>
> I was j
I would look at WAL files as a sequence of commits and not a sequence of
files within timelines where you can specify either with recovery_target_time
or recovery_target_xid the point of consistency you want to reach.
Cheers,
A.A.
On Fri, Sep 6, 2013 at 1:26 PM, John Lumby wrote:
> We use log
I would also give it a try on turning on statistics on service_id and
follower_id fields and tune collecting of distinct values for the optimizer.
Cheers,
Amador A.
On Wed, Apr 24, 2013 at 9:04 AM, François Beausoleil
wrote:
> Hi!
>
> Le 2013-04-17 à 14:15, Jeff Janes a écrit :
>
> On Wed, Apr
