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

Re: stack usage in toast_insert_or_update()

From: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: stack usage in toast_insert_or_update()
Date: 2007-02-01 11:44:56
Message-ID: 2e78013d0702010344n56a560abn577e9d85669f35f1@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 1/31/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

>
> We can't change TOAST_MAX_CHUNK_SIZE without forcing an initdb, but I
> think that it would be safe to remove the MAXALIGN'ing of the tuple
> size in the tests in heapam.c, that is
>
>
That would mean that the tuple size in the heap may exceed
TOAST_TUPLE_THRESHOLD which should be OK, but we
may want to have a comment explaining that.

We should do the same for heap_update() as well.

Thanks,
Pavan

-- 

EnterpriseDB     http://www.enterprisedb.com

In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2007-02-01 11:49:55
Subject: Re: Improving NOT IN
Previous:From: Simon RiggsDate: 2007-02-01 11:33:40
Subject: Re: max_locks_per_transactions ...

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