Re: Status of server side Large Object support? - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: Status of server side Large Object support?
Date
Msg-id 1102466018.4020.11.camel@fuji.krosing.net
Whole thread Raw
In response to Re: Status of server side Large Object support?  (David Garamond <lists@zara.6.isreserved.com>)
Responses Re: Status of server side Large Object support?
List pgsql-hackers
On E, 2004-11-29 at 02:22, David Garamond wrote:
> Joe Conway wrote:
> > Not if the column is storage type EXTERNAL. See a past discussion here:
> > http://archives.postgresql.org/pgsql-general/2003-07/msg01447.php
> 
> what is the reasoning behind this syntax?
> 
>   ALTER TABLE [ ONLY ] table [ * ]
>   ALTER [ COLUMN ] column SET STORAGE
>   { PLAIN | EXTERNAL | EXTENDED | MAIN }
> 
> I find it nonintuitive and hard to remember. Perhaps something like this 
> is better (I know, it's probably too late):
> 
>   ALTER [ COLUMN ] column SET STORAGE { INLINE | EXTERNAL }
>   ALTER [ COLUMN ] column SET COMPRESSION { YES | NO }

It wold also be beneficial if the threshold size of moving the column to
TOAST (either COMPRESS or EXTERNAL) could be set on a per-column basis

This is a design decision on the same lavel as the others

------------
Hannu



pgsql-hackers by date:

Previous
From: Matthias Schmidt
Date:
Subject: Re: somebody working on: Prevent default re-use of sysids for dropped users and groups?
Next
From: Horak Daniel
Date:
Subject: Re: apparent problem on linux/s390