From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>, Robert Haas <robert(dot)haas(at)enterprisedb(dot)com> |
Subject: | Re: [COMMITTERS] pgsql: Improve the -l (limit) option recently added to contrib/vacuumlo |
Date: | 2012-03-21 13:54:53 |
Message-ID: | 29572.1332338093@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> On 21.03.2012 01:05, Tom Lane wrote:
>> Improve the -l (limit) option recently added to contrib/vacuumlo.
> Shouldn't this be backported? Without it, vacuumlo is effectively broken
> in 9.0 and 9.1.
I was wondering about that. You could argue for either "it's a new
feature" or "it's a bug fix". It's a simple enough change that I see
little risk in it, so the argument against backporting seems weak.
If there are not objections, I'll just copy the current vacuumlo code
in toto into 9.0 and 9.1.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-03-21 14:58:07 | pgsql: Improve connectMaintenanceDatabase() error reporting. |
Previous Message | Heikki Linnakangas | 2012-03-21 07:10:28 | Re: [COMMITTERS] pgsql: Improve the -l (limit) option recently added to contrib/vacuumlo |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-03-21 13:59:49 | Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock) |
Previous Message | Robert Haas | 2012-03-21 13:26:58 | Re: Memory usage during sorting |