Re: [SQL] Problem copying polygon data into a table - Mailing list pgsql-sql

From wieck@debis.com (Jan Wieck)
Subject Re: [SQL] Problem copying polygon data into a table
Date
Msg-id m11xPvF-0003kGC@orion.SAPserv.Hamburg.dsh.de
Whole thread Raw
In response to Problem copying polygon data into a table  (Brent Wood <brent.wood@blazemail.com>)
List pgsql-sql
> The polygon has about 800 vertices (& is relatively small as some of the
> polygons in my dataset go).
>
> Trying to copy this into the table generates the error msg:
>
> ERROR: Tuple is too big: size 12892

    It  is  a  very  old  limitation, that one row (including the
    systems per row information and ALL attribute values)  cannot
    exceed 8K - pageheader.

    800  vertices is 1600 double precision floats is 12800 bytes.

    We actually discuss how to tackle that problem  in  a  future
    release.   And  that  far we know about a solution that could
    make your problem go away.  What we don't have is a consensus
    on, and implementation of this solution.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #

pgsql-sql by date:

Previous
From: Tom Lane
Date:
Subject: Re: [SQL] how to tell the difference between empty field and null field
Next
From: Tom Lane
Date:
Subject: Re: [SQL] Problem copying polygon data into a table