On Tue, Mar 01, 2011 at 08:40:37AM -0500, Robert Haas wrote:
> On Mon, Feb 28, 2011 at 10:32 PM, Greg Stark wrote:
> > On Tue, Mar 1, 2011 at 1:43 AM, David Christensen
> > wrote:
> >> Was this cluster upgraded to 8.4.4 from 8.4.0? It sounds to me like a
> >> known bug in 8.4.0 which was fixed
Thanks for the suggestions. I made all of the changes you mentioned except for
the shared_buffers (which will require a downtime I have set for tonight). I do
have another question though, why did you pick 512 MB for the new setting of
shared_buffers? Everything I've ever read says that 25% of a
On Mar 2, 12:02 pm, sco...@openscg.com (Scott Mead) wrote:
> --
> Scott Mead
>
> OpenSCG
> PostgreSQL, Java & Linux Experts
>
> http://openscg.com
>
> On Wed, Mar 2, 2011 at 9:17 AM, Jason Clark
> wrote:
>
>
>
>
>
>
>
>
>
> > Hey fellas,
>
> > A little stumped here, maybe someone could give me som
On Wed, 2011-03-02 at 23:44 -0500, Robert Treat wrote:
> Yeah, it's worth pointing out that either you (the OP) are reading the
> wrong stuff, or interpreting it wrong. 25% is usually where people
> will tell you to start, and then tune it *down* (change, measure,
> asses, repeat).
assess robert.
On Wed, Mar 2, 2011 at 2:04 PM, Kevin Grittner
wrote:
>> "Vaughn, Adam (IMS)" wrote:
>>
>> I made all of the changes you mentioned except for the
>> shared_buffers (which will require a downtime I have set for
>> tonight). I do have another question though, why did you pick 512
>> MB for the new
On Wed, Mar 2, 2011 at 11:17 PM, Jason Clark
wrote:
> so thats not an issue, also, the backup server is pulling the WAL
> files and loading them properly, here is my recovery.conf file:
>
> standby_mode = 'on'
> restore_command = 'usr/pgsql-9.0/bin/pg_standby -d -w 300 -t /tmp/
> trigger.5423 /mnt
On Wed, Mar 02, 2011 at 04:20:24PM -0800, bricklen wrote:
> On Wed, Mar 2, 2011 at 3:53 PM, daveg wrote:
> >> > Postgresql version is 8.4.4.
> >>
> >> I don't see how this could be related, but since you're running on NFS,
> >> maybe it is, somehow:
> >> http://archives.postgresql.org/message-id/4
On Wed, Mar 2, 2011 at 3:53 PM, daveg wrote:
>> > Postgresql version is 8.4.4.
>>
>> I don't see how this could be related, but since you're running on NFS,
>> maybe it is, somehow:
>> http://archives.postgresql.org/message-id/4d40ddb7.1010...@credativ.com
>> (for example what if the visibility ma
On Wed, Mar 02, 2011 at 06:45:13PM -0300, Alvaro Herrera wrote:
> Excerpts from daveg's message of mié mar 02 18:30:34 -0300 2011:
>
> > After a restart and vacuum of all dbs with no other activity things were
> > quiet for a couple hours and then we started seeing these PD_ALL_VISIBLE
> > message
Excerpts from daveg's message of mié mar 02 18:30:34 -0300 2011:
> After a restart and vacuum of all dbs with no other activity things were
> quiet for a couple hours and then we started seeing these PD_ALL_VISIBLE
> messages again.
>
> Going back through the logs we have been getting these sinc
On Tue, Mar 01, 2011 at 01:20:43PM -0800, daveg wrote:
> On Tue, Mar 01, 2011 at 12:00:54AM +0200, Heikki Linnakangas wrote:
> > On 28.02.2011 23:28, daveg wrote:
> > >On Wed, Jan 12, 2011 at 10:46:14AM +0200, Heikki Linnakangas wrote:
> > >>We'll likely need to go back and forth a few times with v
> "Vaughn, Adam (IMS)" wrote:
>
> I made all of the changes you mentioned except for the
> shared_buffers (which will require a downtime I have set for
> tonight). I do have another question though, why did you pick 512
> MB for the new setting of shared_buffers? Everything I've ever
> read says
--
Scott Mead
OpenSCG
PostgreSQL, Java & Linux Experts
http://openscg.com
On Wed, Mar 2, 2011 at 9:17 AM, Jason Clark wrote:
> Hey fellas,
>
> A little stumped here, maybe someone could give me some insight?
>
> I have set up a warm standby situation for testing before rolling it
> out to ou
Hey fellas,
A little stumped here, maybe someone could give me some insight?
I have set up a warm standby situation for testing before rolling it
out to our production servers, the primary database is archiving
properly to a samba share archive using the following archive
command:
'cp %p /mnt/wi
14 matches
Mail list logo