On Thu, Jun 8, 2017 at 1:17 PM, Pavel Stehule wrote:
> 2017-06-08 17:19 GMT+02:00 Robert Haas :
>> On Wed, Jun 7, 2017 at 12:30 PM, Pavel Stehule
>> wrote:
>> > I got strange error message - false message - max connection is less on
>> > slave than on master, although these numbers was same. The
2017-06-08 17:19 GMT+02:00 Robert Haas :
> On Wed, Jun 7, 2017 at 12:30 PM, Pavel Stehule
> wrote:
> > I got strange error message - false message - max connection is less on
> > slave than on master, although these numbers was same. The issue was in
> > wrong connection string in recovery conf a
On Wed, Jun 7, 2017 at 12:30 PM, Pavel Stehule wrote:
> I got strange error message - false message - max connection is less on
> slave than on master, although these numbers was same. The issue was in
> wrong connection string in recovery conf and slave cannot to check master
> and used some defa
Adriaan Joubert <[EMAIL PROTECTED]> writes:
ERROR: UNLockBuffer: buffer 0 is not locked
> Right, I'vebuilt a new database and everything seemed fine for a while and
> now I've got this message back. It is due to the index on one of our
> tables getting messed up - at least, if we drop and r
Tom Lane wrote:
> Adriaan Joubert <[EMAIL PROTECTED]> writes:
> > we've suddenly started getting this error message out of postgres
> > (7.0.2). Does anybody know where it comes from?
>
> > ERROR: UNLockBuffer: buffer 0 is not locked
>
> Evidently something is passing an invalid buffer numbe
Adriaan Joubert <[EMAIL PROTECTED]> writes:
> we've suddenly started getting this error message out of postgres
> (7.0.2). Does anybody know where it comes from?
> ERROR: UNLockBuffer: buffer 0 is not locked
Evidently something is passing an invalid buffer number to LockBuffer
in src/backen
