On Fri, 27 Oct 2000 11:55:24 -0700, Darcy Buskermolen said:
> Could it also be the result of a Cluster operation? I've seen strange
> things related to functions/triggers on tables that I've clustered.
Personally for me it turned out to be, as Tom said, the
renaming of a table involving
Could it also be the result of a Cluster operation? I've seen strange
things related to functions/triggers on tables that I've clustered.
>> At a guess, you've run into the known bug that foreign key triggers
>> don't track renames of referenced tables. Did you rename a table that
>> is a forei
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Do we need a TODO here?
None that we haven't got already, AFAIK.
regards, tom lane
Do we need a TODO here?
> Sean Kelly <[EMAIL PROTECTED]> writes:
> > (gdb) bt
> > #0 0x8115eb2 in ri_BuildQueryKeyFull ()
> > #1 0x8115dc2 in RI_FKey_keyequal_upd ()
> > #2 0x8096d7c in DeferredTriggerSaveEvent ()
>
> Hmm. There wasn't any mention of foreign keys for this table in your
> bug
On Thu, 26 Oct 2000 11:27:22 -0400, Tom Lane said:
> Sean Kelly <[EMAIL PROTECTED]> writes:
> > (gdb) bt
> > #0 0x8115eb2 in ri_BuildQueryKeyFull ()
> > #1 0x8115dc2 in RI_FKey_keyequal_upd ()
> > #2 0x8096d7c in DeferredTriggerSaveEvent ()
>
> Hmm. There wasn't any mention of foreign
Sean Kelly <[EMAIL PROTECTED]> writes:
> (gdb) bt
> #0 0x8115eb2 in ri_BuildQueryKeyFull ()
> #1 0x8115dc2 in RI_FKey_keyequal_upd ()
> #2 0x8096d7c in DeferredTriggerSaveEvent ()
Hmm. There wasn't any mention of foreign keys for this table in your
bug report, now was there?
At a guess, you'
On Thu, 26 Oct 2000 10:14:16 -0400, Tom Lane said:
> gdb /path/to/postgres-executable /path/to/core-file
> bt
> quit
[postgres@nis-master] ~
132: gdb bin/postgres data/base/users/core
This GDB was configured as "i386-slackware-linux"...
Core was generated by `/usr/local/po
Sean Kelly <[EMAIL PROTECTED]> writes:
> Ok, I sorted that ... I now have a 2Mb core file. Can you
> explain how to 'backtrace' it with gdb ...
gdb /path/to/postgres-executable /path/to/core-file
bt
quit
and send the results. Hopefully there will be at least funct
On Wed, 25 Oct 2000 14:14:22 -0400, Tom Lane said:
> >No core there ... any other suggestions?
>
> You probably started the postmaster with a ulimit setting that prevents
> coredumps (ulimit -c 0 or something like that, see your ulimit man page).
> On some Unixen, this ulimit setting is
Sean Kelly <[EMAIL PROTECTED]> writes:
>> This backend crash should have left a core file in your database
>> directory (PGDATA/base/users/core). Can you provide a backtrace
>> from that corefile using gdb?
> No core there ... any other suggestions?
You probably started the postmaster wit
On Wed, 25 Oct 2000 12:52:44 -0400, Tom Lane said:
> [EMAIL PROTECTED] writes:
> > users=> update users_tbl set added=TRUE where username like 'neta%';
> > pqReadData() -- backend closed the channel unexpectedly.
>
> > bash$ tail ~postgres/server.log
> > Server process (pid 23747) exited wi
[EMAIL PROTECTED] writes:
> users=> update users_tbl set added=TRUE where username like 'neta%';
> pqReadData() -- backend closed the channel unexpectedly.
> bash$ tail ~postgres/server.log
> Server process (pid 23747) exited with status 11 at Tue Oct 24 13:52:29 2000
This backend crash should h
Here is a debug (level 2) output - does this help any
more?... If not, what should I provide for you in terms of
debugging?...
FindExec: found "/usr/local/postgres/bin/postgres" using argv[0]
binding ShmemCreate(key=52e2c1, size=1104896)
DEBUG: Data Base System is starting up at Wed Oc
> Here is a debug (level 2) output - does this help any
> more?... If not, what should I provide for you in terms of
> debugging?...
Hmm. I didn't find the update/select combination you specified in your
problem statement in your debugging output, but it wouldn't have likely
helped anywa
> Short Description
> Updating multiple bool values crashes backend
I cannot reproduce this example with 7.0.2 on my Linux-2.2.16 laptop. We
will need more details and a reproducible example to help out...
- Thomas
Sean Kelly ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
Updating multiple bool values crashes backend
Long Description
Bug best described by an example, see below.
Tested on two systems:
Intel Pentium III 600
128Mb RAM
Linu
16 matches
Mail list logo
