Re: buffer overflow (I'm getting it too!)

I have no answer to this, but I'll add my experience to the question.

I'm getting the same message, but in my case it is not consistent. It is
always during a cron job that does a vacuum analyze in the middle of the
night, but not every time the job runs. If I do the same thing interactively
(the vacuum/analyze), I don't get the message, so I only see the messages
about once a week & can't reproduce the problem reliably.

It doesn't appear that anything is "broken" when we get this message-
everything keeps running well.

Any thoughts?

Thanks

-Nick

> -----Original Message-----
> From: pgsql-admin-owner(at)postgresql(dot)org
> [mailto:pgsql-admin-owner(at)postgresql(dot)org]On Behalf Of Laurette Cisneros
> Sent: Wednesday, October 03, 2001 12:33 PM
> To: pgsql-admin(at)postgresql(dot)org
> Subject: [ADMIN] buffer overflow
>
>
>
> I am consistently getting these NOTICEs as I work with postgresql
> 7.1.2 and 7.1.3.
>
> NOTICE: RegisterSharedInvalid: SI buffer overflow
> NOTICE: RegisterSharedInvalid: SI buffer overflow
> NOTICE: InvalidateSharedInvalid: cache state reset
> NOTICE: RegisterSharedInvalid: SI buffer overflow
> NOTICE: InvalidateSharedInvalid: cache state reset
> ...
> psql:/tmp/laurette23849/jobseq.sql:23228: NOTICE:
> InvalidateSharedInvalid: cache state reset
> psql:/tmp/laurette23849/jobseq.sql:23228: NOTICE:
> InvalidateSharedInvalid: cache state reset
>
> What can be done to "fix" them?
>
> Thanks,
>
> --
> Laurette Cisneros
> (510) 420-3137
> NextBus Information Systems, Inc.
> www.nextbus.com
> Passenger Information Everywhere
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>