Re: [BUGS] Backend crash while indexing large strings

2001-02-12 Thread Stephen van Egmond
Tom Lane ([EMAIL PROTECTED]) wrote: > I get > > FATAL 1: btree: failed to add item to the page in _bt_sort (2) > pqReadData() -- backend closed the channel unexpectedly. > This probably means the backend terminated abnormally > before or while processing the request. > > Is that

Re: [BUGS] comments on columns aren't displayed by \dd

2001-03-20 Thread Stephen van Egmond
Bruce Momjian ([EMAIL PROTECTED]) wrote: > Psql manual pages says: > > The command form \d+ is identical, but any comments > associated with the table columns are shown as > well. Thank you for the response, Bruce. I was working from the HTML docs

[BUGS] BUG #2667: vacuuming a 70GB table causes a "crash"

2006-09-30 Thread Stephen R. van den Berg
The following bug has been logged online: Bug reference: 2667 Logged by: Stephen R. van den Berg Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.4 Operating system: Linux 2.6.16.20 Debian (pg: 8.1.4-6) Description:vacuuming a 70GB table causes a "

Re: [BUGS] BUG #2667: vacuuming a 70GB table causes a "crash"

2006-10-01 Thread Stephen R. van den Berg
On 9/30/06, Tom Lane <[EMAIL PROTECTED]> wrote: "Stephen R. van den Berg" <[EMAIL PROTECTED]> writes: > datalog=# vacuum verbose fnetsense; > INFO: vacuuming "public.fnetsense" > PANIC: right sibling is not next child in "fnetsense_utstamp_ke

[BUGS] Referential integrity problem postgresql 7.2 ?

2002-06-11 Thread Stephen R. van den Berg
deferred); insert into a values (7); begin; insert into b values (-7); update b set ia=-ia where ia<0; commit; drop table a; drop table b; -- Sincerely, [EMAIL PROTECTED] Stephen R. van den Berg (AKA BuGless). "-- hit

<    1   2