| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Relation 0 does not exist |
| Date: | 2002-09-25 21:49:17 |
| Message-ID: | 28331.1032990557@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> writes:
> One thing which bugs me: I have a currval in there, and that is the very
> first query which reaches the database, so it won't be "set", will it, but
> then, how could it have worked for months with the other version of server?
Good question. Do you have any ON INSERT rules on that table?
Could you try setting a breakpoint at elog() to capture the stack trace
leading up to the error? (Note elog() will be called for each log entry
that's made, so if you just set the breakpoint at the start of the
routine, you'll have to 'continue' several times until the actual ERROR
call occurs.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Patrick Welche | 2002-09-25 21:56:44 | Re: "lo" large object |
| Previous Message | Adahma | 2002-09-25 21:43:02 | Re: Error at startup |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2002-09-25 22:04:39 | compiling client utils under win32 - current 7.3devel is broken |
| Previous Message | Patrick Welche | 2002-09-25 21:29:49 | Re: Relation 0 does not exist |