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

Re: Efficient slicing/substring of TOAST values (for

From: John Gray <jgray(at)azuli(dot)co(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Efficient slicing/substring of TOAST values (for
Date: 2001-10-11 23:43:46
Message-ID: 1002843827.21634.39.camel@adzuki (view raw or flat)
Thread:
Lists: pgsql-patches
On Thu, 2001-10-11 at 04:54, Tom Lane wrote:

> Sounds like a great idea --- the ALTER TABLE code has kind of grown
> without supervision over the past few releases, since cut-and-paste
> was the easiest starting point for implementing any new variant.
> Some creative refactoring would help it out a lot.  Go for it, if
> you feel like doing that.
> 
I've done a little tidying, repackaging of standard code etc. as a first
step. It hasn't made the file much shorter, but has made some of the
routines clearer where they share basically the same code for
inheritance and permissions checking.

AS regards the ALTER TABLE ALTER COLUMN syntax for attstorage, should I
use keywords for the values or just char values 'e', 'x' etc ?

ALTER TABLE example ALTER COLUMN test SET STORAGE EXTERNALPLAIN;
or
ALTER TABLE example ALTER COLUMN test SET STORAGE 'e';

(if anyone has any views on a better keyword than STORAGE...)

Obviously I'll have to get to grips with the parser next (which will be
a novelty as I don't have any familiarity with lex/yacc)

Regards

John



In response to

Responses

pgsql-patches by date

Next:From: Ricardo Caesar LenziDate: 2001-10-11 23:44:58
Subject: PyGreSQL v3.2 doesn't support INT8 types
Previous:From: Adam OsuchowskiDate: 2001-10-11 22:24:45
Subject: psql: default base and password reading

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