Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: postmaster segfault when using SELECT on a table
- From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: Karsten Desler <kd(at)link11(dot)de>, pgsql-bugs(at)postgresql(dot)org
- Subject: Re: postmaster segfault when using SELECT on a table
- Date: Mon, 28 Apr 2008 13:31:20 +0200
- Message-id: <4815B588(dot)5090502(at)sun(dot)com>
Tom Lane wrote:
My suspicion though is that you'll find that a large portion of that page is damaged; that's usually what we've seen in such cases in the past.
I think, It can happen only if corruption is less then TOAST chunk size. In other case, page header or tuple header+chunk id should be corrupted and it should be reported in another place.
Zdenek
- References:
- postmaster segfault when using SELECT on a table
- From: Karsten Desler
- Re: postmaster segfault when using SELECT on a table
- From: Tom Lane
- Re: postmaster segfault when using SELECT on a table
- From: Karsten Desler
- Re: postmaster segfault when using SELECT on a table
- From: Tom Lane
- postmaster segfault when using SELECT on a table
- Prev by Date: Re: postmaster segfault when using SELECT on a table
- Next by Date: PB with postgresql 7.4
- Previous by thread: Re: postmaster segfault when using SELECT on a table
- Next by thread: Re: postmaster segfault when using SELECT on a table
- Indexes: