| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(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: Patch queue triage |
| Date: | 2007-05-17 17:26:52 |
| Message-ID: | 2e78013d0705171026x21708335hc5d673b162815b17@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/17/07, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>
> Pavan Deolasee wrote:
>
> >
> >
> > There are few things that we can separate easily, like CREATE INDEX
> > related changes, VACUUM and VACUUM FULL related changed, space
> > reuse related changes etc. Let me give it a shot.
>
> Did we ever get a broken up patch for this?
I broke the patch into 5 smaller, logical pieces and posted them
on May 7th.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-05-17 17:27:09 | Re: Patch queue triage |
| Previous Message | Bruce Momjian | 2007-05-17 17:26:27 | Re: Patch queue triage |