Skip site navigation (1) Skip section navigation (2)

Too large tuples corrupting tables

From: Daniel Stolk <stolkd(at)email(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Too large tuples corrupting tables
Date: 1999-12-06 20:07:20
Message-ID: 384C1777.D6ADA5B2@email.com (view raw or flat)
Thread:
Lists: pgsql-bugs
============================================================================
                        POSTGRESQL BUG REPORT TEMPLATE
============================================================================


Your name		:	Daniel Stolk
Your email address	:   stolkd(at)email(dot)com


System Configuration
---------------------
  Architecture (example: Intel Pentium)  	:  AMD K6 300MHz

  Operating System (example: Linux 2.0.26 ELF) 	:  Red Hat 6.0 with
Linux 2.2.5-15

  PostgreSQL version (example: PostgreSQL-6.5.1):   PostgreSQL-6.5.1

  Compiler used (example:  gcc 2.8.0)		:  egcs-2.91.66


Please enter a FULL description of your problem:
------------------------------------------------

I seem to have a problem here.  When I try to insert a tuple
that is
larger than 8192 bytes, I get an error message saying that the
tuple is
too large.  Ok, that's fine, since the BLCK_SIZE is 8192.
But the problem is that the
table seems to
become corrupted.  After I do this insert statement I went to
psql and
did a select on the table (which doesn't have any tuples in
it).  So far
so good.  But then I inserted a tuple that wasn't too large
and when I
did a select on the table, I got an error message about the
backend
going down or something like that.  However, I then inserted
another
tuple (again one that wasn't too large) into the table and it seemed to
go fine
and when I looked at the file size of that table in the
database's data
directory, the size went up.  So the insert seems to still
work but the
select doesn't?!?!  What's going on here?  Please let me know
if this isn't a bug, but something that I need to work around or
something I need to do differently.  I posted this to the 'general' 
mailing list and got no replies.  Thanks.



Please describe a way to repeat the problem.   Please try to provide a
concise reproducible example, if at all possible: 
----------------------------------------------------------------------

I guess you should be able to recreate this problem quite easily from
the
statement above.  If not, then let me know, maybe I'm doing something
wrong
or different.



If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------

pgsql-bugs by date

Next:From: Richard PooleDate: 1999-12-07 00:04:45
Subject: renaming index leaves database inconsistent
Previous:From: Assaf GottliebDate: 1999-12-06 13:55:09
Subject: OLE-DB vs. ODBC performance on SQL Server 7.0:

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group