Re: Efficient slicing/substring of TOAST values (for comment) - Mailing list pgsql-patches

From Tom Lane
Subject Re: Efficient slicing/substring of TOAST values (for comment)
Date
Msg-id 22931.1002845820@sss.pgh.pa.us
Whole thread Raw
In response to Re: Efficient slicing/substring of TOAST values (for  (John Gray <jgray@azuli.co.uk>)
Responses Re: Efficient slicing/substring of TOAST values (for comment)  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
John Gray <jgray@azuli.co.uk> writes:
>> 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.

Great!  I'm afraid I just committed some fixes that will probably cause
a merge conflict, but I trust it won't be too painful to resolve.

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

I'd suggest keywords, namely the same ones used in CREATE TYPE for
these storage options.

            regards, tom lane

pgsql-patches by date:

Previous
From: John Gray
Date:
Subject: Re: Efficient slicing/substring of TOAST values (for
Next
From: Bruce Momjian
Date:
Subject: Re: postgresql-7.1.3 pg_ctl password authentication and startup