Merlin Moncure wrote:
> n 2/6/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> >Merlin Moncure wrote:
> >
> >> ya, it doesn't seem to match, as this seems to be repeating quite
> >> regularly. interesting that my 'clog' files start at 06B6 and count
> >> up. 0207 is way off the charts.
> >>
> >> a
n 2/6/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
Merlin Moncure wrote:
> ya, it doesn't seem to match, as this seems to be repeating quite
> regularly. interesting that my 'clog' files start at 06B6 and count
> up. 0207 is way off the charts.
>
> a lot of applications are hitting this databa
Merlin Moncure wrote:
> ya, it doesn't seem to match, as this seems to be repeating quite
> regularly. interesting that my 'clog' files start at 06B6 and count
> up. 0207 is way off the charts.
>
> a lot of applications are hitting this database, and so far everything
> seems to be running ok (i
On 2/6/07, Stefan Kaltenbrunner <[EMAIL PROTECTED]> wrote:
Merlin Moncure wrote:
> On 2/6/07, Merlin Moncure <[EMAIL PROTECTED]> wrote:
>> around 6:30 this morning, I started getting the following messages in
>> my log:
>>
>> Feb 6 06:33:34 mojo postgres[1117]: [2-1] :: ERROR: could not access
Merlin Moncure wrote:
> On 2/6/07, Merlin Moncure <[EMAIL PROTECTED]> wrote:
>> around 6:30 this morning, I started getting the following messages in
>> my log:
>>
>> Feb 6 06:33:34 mojo postgres[1117]: [2-1] :: ERROR: could not access
>> status of transaction 51911
>> Feb 6 06:34:35 mojo po
On 2/6/07, Merlin Moncure <[EMAIL PROTECTED]> wrote:
around 6:30 this morning, I started getting the following messages in my log:
Feb 6 06:33:34 mojo postgres[1117]: [2-1] :: ERROR: could not access
status of transaction 51911
Feb 6 06:34:35 mojo postgres[1128]: [2-1] :: ERROR: could no
