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

Re: PATCH: optimized DROP of multiple tables within a transaction

From: Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>
To: Tomas Vondra <tv(at)fuzzy(dot)cz>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PATCH: optimized DROP of multiple tables within a transaction
Date: 2013-01-09 07:03:44
Message-ID: CAEZqfEdi52yfyZPrqgGA+4EQP7jW3dsaCFQet-sBNKyD7_QDbw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Hi Tomas,

On Wed, Jan 9, 2013 at 6:38 AM, Tomas Vondra <tv(at)fuzzy(dot)cz> wrote:
>> Well, you need to ensure that the initial palloc is an array of that
>> size.
>
> Oh, right - I forgot to modify the palloc() call. Thanks for spotting
> this. Attached is a patch with increased threshold and fixed palloc call.

OK, both threshold and initial palloc were fixed correctly.

I'll mark this patch as "Ready for committer".
Good work! :-)

Regards,
-- 
Shigeru HANADA


In response to

pgsql-hackers by date

Next:From: Benedikt GrundmannDate: 2013-01-09 07:56:12
Subject: Re: Improve compression speeds in pg_lzcompress.c
Previous:From: Josh BerkusDate: 2013-01-09 06:01:58
Subject: Re: PL/perl should fail on configure, not make

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