On Fri, Jun 10, 2005 at 12:34:15PM -0400, Tom Lane wrote:
> "Colin E. Freas" <[EMAIL PROTECTED]> writes:
> > 2005-06-07 16:02:38 EDTLOG: statement: update pg_class set
> > reltriggers=foo.c from (select relname,count(tgrelid) as c from
> > pg_class,pg_trigger where pg_class.oid=tgrelid and relna
"Colin E. Freas" <[EMAIL PROTECTED]> writes:
> 2005-06-07 16:02:38 EDTLOG: statement: update pg_class set
> reltriggers=foo.c from (select relname,count(tgrelid) as c from
> pg_class,pg_trigger where pg_class.oid=tgrelid and relnamespace=2200
> group by relname) foo;
I'm afraid that database i
Sorry if this post winds up as a duplicate on the list...
---
In an effort to disable all of the foreign key restraints on a set of
tables in my installation of PostgreSQL 8.0.1, I was fiddling with the
pg_class table and managed to elicit behavior similar to what L.
Boldareva ran into.
(T
On Fri, 1 Apr 2005, Tom Lane wrote:
> "L.Boldareva" <[EMAIL PROTECTED]> writes:
> > Here is how I got it crashed:
> > I compiled a c-procedure and copied the .so file to its place exactly at a
> > time when (quite unfortunately) another query was running, that used that
> > library.
>
> Hmm, at w
"L.Boldareva" <[EMAIL PROTECTED]> writes:
> Here is how I got it crashed:
> I compiled a c-procedure and copied the .so file to its place exactly at a
> time when (quite unfortunately) another query was running, that used that
> library.
Hmm, at worst that should only crash one backend, not result
I have kind of fixed the problem (hopefully)
I turned out I used plan B, dump/reload will be my next step then.
What is meant by the "corrupt data", is this about the data or the things
around it, like indexes, system tables?
Here is how I got it crashed:
I compiled a c-procedure and copied the .
On Fri, 2005-04-01 at 04:02, L.Boldareva wrote:
> Hi!
> (Hope this is the right place to post)
>
> I crashed the postmaster and cannot start it anymore, with the error
In addition to what everyone's posted already, I would suggest you spend
some time figuring out what got you here in the first pl
Ok, looks like I kind of fixed it.
(after tarring data/) I ran pg_resetxlog -f , although it's not meant to
fix this problem.
The database starts up now, but the last created couple of tables are
coppupted, so that it cannot be reindexed or vaccumed, and
there is an error in a system table:
Pos
"L.Boldareva" <[EMAIL PROTECTED]> writes:
> LOG: database system was not properly shut down; automatic recovery in
> progress
> LOG: redo starts at 5/6F000ABC
> PANIC: btree_split_redo: lost left sibling
> LOG: startup process (PID 5603) was terminated by signal 6
Hmm. AFAICS that could only
"L.Boldareva" <[EMAIL PROTECTED]> wrote on 01.04.2005, 12:02:21:
> Hi!
> (Hope this is the right place to post)
>
> I crashed the postmaster and cannot start it anymore, with the error
>
> LOG: database system was interrupted while in recovery at 2005-04-01
> 11:04:33 CEST
> HINT: This proba
Hi!
(Hope this is the right place to post)
I crashed the postmaster and cannot start it anymore, with the error
LOG: database system was interrupted while in recovery at 2005-04-01 11:04:33
CEST
HINT: This probably means that some data is corrupted and you will have to use
the last backup fo
11 matches
Mail list logo
