From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Ricardo Vaz Mannrich <rvm_l1(at)uol(dot)com(dot)br> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: err: backend closed the channel unexpectedly |
Date: | 2002-04-01 19:43:48 |
Message-ID: | 20020401114201.A51949-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 1 Apr 2002, Ricardo Vaz Mannrich wrote:
> I have a database with four tables (here named tab1, tab2, tab3 and
> hawb_extra).
>
> tab1 has 322556 rows,
> tab2 has 334394,
> tab3 has 2360079,
> and hawb_extra has 472906.
>
> hawb_extra is fulled by triggers on tab1, tab2 and tab2 using INSERTs and
> UPDATEs.
>
> I had an index on hawb_extra using data_col and locatual fields and when I
> tried to run a query using these fields, PG didn't used index scan. So, I
> dropped and tried to create again the index. See what I get. I tried a lot of
> times. Thanks for your help:
It'd probably be helpful to get a backtrace from the core this should have
produced in your database directory (if it didn't produce a core, you may
need to change your user limits to get one).
From | Date | Subject | |
---|---|---|---|
Next Message | Nic Ferrier | 2002-04-01 19:46:55 | Re: NOT IN queries |
Previous Message | Ricardo Vaz Mannrich | 2002-04-01 18:56:59 | err: backend closed the channel unexpectedly |