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
Hi
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 defaults.
Regards
Pavel
> 2) The constraint doesn't exist on the master, only the slave, so I don't
> beleive EXECUTE SCRIPT will work, no?
No, it does not work. I've tried.
// John
_
John Parnefjord
Samordnare UBIT Utveckling / Coordinator UBIT Development
> Ühel kenal päeval, R, 2007-10-19 kell 15:29, kirjutas Magnus Hagander:
> > On Thu, Oct 18, 2007 at 10:48:02AM -0400, Tom Lane wrote:
> > > "Magnus Hagander" <[EMAIL PROTECTED]> writes:
> > > > db=# alter table isi.items_stat drop constraint items_stat_item_id_fkey;
> > > > ERROR: "items_pkey" is
Ühel kenal päeval, R, 2007-10-19 kell 15:29, kirjutas Magnus Hagander:
> On Thu, Oct 18, 2007 at 10:48:02AM -0400, Tom Lane wrote:
> > "Magnus Hagander" <[EMAIL PROTECTED]> writes:
> > > db=# alter table isi.items_stat drop constraint items_stat_item_id_fkey;
> > > ERROR: "items_pkey" is an index
On Thu, Oct 18, 2007 at 10:48:02AM -0400, Tom Lane wrote:
> "Magnus Hagander" <[EMAIL PROTECTED]> writes:
> > db=# alter table isi.items_stat drop constraint items_stat_item_id_fkey;
> > ERROR: "items_pkey" is an index
>
> Context please?
Yeah, I had that one coming, didn't it... That's what I g
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> db=# alter table isi.items_stat drop constraint items_stat_item_id_fkey;
> ERROR: "items_pkey" is an index
Context please?
regards, tom lane
---(end of broadcast)---
TIP 4: Ha
db=# alter table isi.items_stat drop constraint items_stat_item_id_fkey;
ERROR: "items_pkey" is an index
The foreign key points to items.Item_id which is what's indexed by items_pkey.
But I only wanted to drop that constraint.
/Magnus
---(end of broadcast)-
Alessio Bragadini <[EMAIL PROTECTED]> writes:
> FATAL 2: ZeroFill(/data/postgres/pg_xlog/xlogtemp.1223) failed: No such
> file or directory
I think you ran out of disk space. The error message is misleading :-(
regards, tom lane
---(end of broad
hubert depesz lubaczewski <[EMAIL PROTECTED]> writes:
> ERROR: newses_seq.nextval: bad magic ()
Hmm, something bad has happened to your sequence object.
It would be interesting to try to figure out what caused that, but if
you're in a hurry, try dropping and recreating that sequence.
Hi all!
I'm using the PostgreSQL 7.03 and PHP 4.x to create a DB driven site, which
is intended to work under RedHat.
And I often get very strange errors like
"Warning: PostgreSQL query failed: pqReadData() -- read() failed:
errno=32 Broken pipe in /usr/local/home/httpd/htdocs/zyx/xyz.php on
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
Hi,
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
Any help appreciated,
Adriaan
17 matches
Mail list logo
