Re: Vacuumdb Fails: Huge Tuple

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: APseudoUtopia <apseudoutopia(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Subject: Re: Vacuumdb Fails: Huge Tuple
Date: 2009-10-02 15:30:23
Message-ID: 18816.1254497423@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Teodor Sigaev <teodor(at)sigaev(dot)ru> writes:
> Patch removes checking of TOAST_INDEX_TARGET and use checking only by
> GinMaxItemSize which is greater than TOAST_INDEX_TARGET. All size's check is now
> in GinFormTuple.

Looks reasonable, although since the error is potentially user-facing
I think we should put a bit more effort into the error message
(use ereport and make it mention the index name, at least --- is there
any other useful information we could give?)

Will you apply this, or do you want me to?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2009-10-02 16:23:15 Re: Understanding 'could not read block'
Previous Message Teodor Sigaev 2009-10-02 15:19:12 Re: Vacuumdb Fails: Huge Tuple