pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
FATAL 1: btree: items are out of order (leftmost 0, stack 48, update 2)
4+ messages / 3 participants
[nested] [flat]

* FATAL 1: btree: items are out of order (leftmost 0, stack 48, update 2)
@ 2001-02-07 22:41  Michael Miyabara-McCaskey <mykarz@miyabara.com>
  0 siblings, 2 replies; 4+ messages in thread

From: Michael Miyabara-McCaskey @ 2001-02-07 22:41 UTC (permalink / raw)
  To: pgsql-sql; pgsql-admin@postgresql.org

FATAL 1:  btree: items are out of order (leftmost 0, stack 48, update 2)
pqReadData() -- backend closed the channel unexpectedly.
        This probably means the backend terminated abnormally
        before or while processing the request.


Anyone have any ideas?

I was running a script that calls "uc" from Perl... It runs for a while then
I get this error.

PGSQL 7.0.3, Linux RH 6.2 (2.2.17-RAID), 1GB MEM (gets to about 300MB of RAM
used then dies).

Michael Miyabara-McCaskey
Email: mykarz@miyabara.com
Web: http://www.miyabara.com/mykarz/
Mobile: +1 408 504 9014




^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: [SQL] FATAL 1: btree: items are out of order (leftmost 0, stack 48, update 2)
@ 2001-02-07 23:52  Jie Liang <jliang@ipinc.com>
  parent: Michael Miyabara-McCaskey <mykarz@miyabara.com>
  1 sibling, 0 replies; 4+ messages in thread

From: Jie Liang @ 2001-02-07 23:52 UTC (permalink / raw)
  To: Michael Miyabara-McCaskey <mykarz@miyabara.com>; +Cc: pgsql-sql; pgsql-admin@postgresql.org



Jie LIANG

Internet Products Inc.

10350 Science Center Drive
Suite 100, San Diego, CA 92121
Office:(858)320-4873

jliang@ipinc.com
www.ipinc.com

On Wed, 7 Feb 2001, Michael Miyabara-McCaskey wrote:
*************************
if it occurs everytime you run the uc, then you 'd better check your
script or run it in debug mode to figure out the problem.
 
> FATAL 1:  btree: items are out of order (leftmost 0, stack 48, update 2)

**************************
following message seems to me that your postgres master dead!

> pqReadData() -- backend closed the channel unexpectedly.
>         This probably means the backend terminated abnormally
>         before or while processing the request.
> 
> 
> Anyone have any ideas?
> 
> I was running a script that calls "uc" from Perl... It runs for a while then
> I get this error.
> 
> PGSQL 7.0.3, Linux RH 6.2 (2.2.17-RAID), 1GB MEM (gets to about 300MB of RAM
> used then dies).
> 
> Michael Miyabara-McCaskey
> Email: mykarz@miyabara.com
> Web: http://www.miyabara.com/mykarz/
> Mobile: +1 408 504 9014
> 




^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: FATAL 1: btree: items are out of order (leftmost 0, stack 48, update 2)
@ 2001-02-08 00:41  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Michael Miyabara-McCaskey <mykarz@miyabara.com>
  1 sibling, 1 reply; 4+ messages in thread

From: Tom Lane @ 2001-02-08 00:41 UTC (permalink / raw)
  To: mykarz@miyabara.com; +Cc: pgsql-sql; pgsql-admin@postgresql.org

"Michael Miyabara-McCaskey" <mykarz@miyabara.com> writes:
> FATAL 1:  btree: items are out of order (leftmost 0, stack 48, update 2)

This appears to indicate that you've got a corrupted index, possibly due
to carelessness about starting the postmaster always in the same locale
(see past discussions about effects of locale on index sort order).

If you can determine which index is broken, dropping and rebuilding it
should get you out of trouble.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* RE: FATAL 1: btree: items are out of order (leftmost 0, stack 48, update 2)
@ 2001-02-08 06:22  Michael Miyabara-McCaskey <mykarz@miyabara.com>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 4+ messages in thread

From: Michael Miyabara-McCaskey @ 2001-02-08 06:22 UTC (permalink / raw)
  To: 'Tom Lane' <tgl@sss.pgh.pa.us>; +Cc: pgsql-sql; pgsql-admin@postgresql.org

Tom,

Once again you are a lifesaver.

Thank you.  I ended up just dropping all the indexes on the table in
question, and life is now good.

-Michael

> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Wednesday, February 07, 2001 4:42 PM
> To: mykarz@miyabara.com
> Cc: pgsql-sql@postgresql.org; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] FATAL 1: btree: items are out of order
> (leftmost 0,
> stack 48, update 2)
>
>
> "Michael Miyabara-McCaskey" <mykarz@miyabara.com> writes:
> > FATAL 1:  btree: items are out of order (leftmost 0, stack
> 48, update 2)
>
> This appears to indicate that you've got a corrupted index,
> possibly due
> to carelessness about starting the postmaster always in the
> same locale
> (see past discussions about effects of locale on index sort order).
>
> If you can determine which index is broken, dropping and rebuilding it
> should get you out of trouble.
>
> 			regards, tom lane
>




^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2001-02-08 06:22 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2001-02-07 22:41 FATAL 1: btree: items are out of order (leftmost 0, stack 48, update 2) Michael Miyabara-McCaskey <mykarz@miyabara.com>
2001-02-07 23:52 ` Jie Liang <jliang@ipinc.com>
2001-02-08 00:41 ` Tom Lane <tgl@sss.pgh.pa.us>
2001-02-08 06:22   ` Michael Miyabara-McCaskey <mykarz@miyabara.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox