| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCHES] Trivial patch to double vacuum speed |
| Date: | 2006-09-04 22:53:19 |
| Message-ID: | 200609042253.k84MrJp19066@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Alvaro Herrera wrote:
> > > I see the no-index case now:
> > >
> > > + if (nindexes)
> > > + LockBuffer(buf, BUFFER_LOCK_SHARE);
> > > + else
> > > + LockBufferForCleanup(buf);
> > >
> > > Let's see what Greg says, or revert.
> >
> > Hm, that's a good point. I could return it to the original method where it
> > released the share lock and did he LockBufferForCleanup only if necessary. I
> > thought it was awkward to acquire a lock then release it to acquire a
> > different lock on the same buffer but it's true that it doesn't always have to
> > acquire the second lock.
>
> This rush to apply patches just because no one seems to be capable of
> keeping up with them not being reviewed, is starting to get a bit
> worrisome.
When things are placed in the patches queue, I need to get feedback if
there is a problem with them. I am not sure what other process we can
follow, unless we just keep patches there indefinitely, or just ignore
them and never place them in the queue.
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-09-04 23:13:28 | Re: Information schema - finalize key_column_usage |
| Previous Message | Tom Lane | 2006-09-04 22:51:50 | Erratic failures on buildfarm member leveret |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-09-04 23:13:28 | Re: Information schema - finalize key_column_usage |
| Previous Message | Alvaro Herrera | 2006-09-04 22:11:53 | Re: [PATCHES] Trivial patch to double vacuum speed on tables with no indexes |