Re: vacuumlo patch

Поиск
Список
Период
Сортировка
От David Fetter
Тема Re: vacuumlo patch
Дата
Msg-id 20110726162759.GC18160@fetter.org
обсуждение исходный текст
Ответ на Re: vacuumlo patch  ("Timothy D. F. Lewis" <elatllat@gmail.com>)
Список pgsql-hackers
On Tue, Jul 26, 2011 at 12:18:31PM -0400, Timothy D. F. Lewis wrote:
> On Mon, Jul 25, 2011 at 7:28 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> 
> > On Mon, Jul 25, 2011 at 9:37 AM, Tim <elatllat@gmail.com> wrote:
> > > Updated the patch to also apply when the no-action flag is enabled.
> >
> > You may want to read this:
> >
> > http://wiki.postgresql.org/wiki/Submitting_a_Patch
> >
> > And add your patch here:
> >
> > https://commitfest.postgresql.org/action/commitfest_view/open
> >
> > --
> > Robert Haas
> > EnterpriseDB: http://www.enterprisedb.com
> > The Enterprise PostgreSQL Company
> 
> I'm not sure what David did for me so as per Roberts suggestion I have
> added<https://commitfest.postgresql.org/action/patch_view?id=609>this
> patch to the commit fest.
> I'm hoping I have not put this patch in more than one
> workflow<http://wiki.postgresql.org/wiki/Submitting_a_Patch#Patch_review_and_commit>
> .

I just put your name as you've asked me to phrase it into the "pending
patches" part of the PostgreSQL Weekly News.

Thanks for the contribution, and here's hoping your experience here
will be pleasant and productive :)

Cheers,
David.

p.s.  We don't top-post on the PostgreSQL mailing lists.  As with the
customary "reply-to-all," it's a convention we've decided works well
for us. :)
-- 
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: write scalability
Следующее
От: Pavan Deolasee
Дата:
Сообщение: Re: write scalability