Re: Libxml2 load error on Windows

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Talha Bin Rizwan <talha(dot)rizwan(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Libxml2 load error on Windows
Date: 2012-06-19 08:40:58
Message-ID: CA+OCxoywdsa-PqJ0948DnRDrCyBUxAapm0qefynmvQyk9Viq9w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 19, 2012 at 4:43 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
>
> Please add this patch here so that it doesn't get lost in the shuffle:
>
> https://commitfest.postgresql.org/action/commitfest_view/open

Hmm, that raises an interesting question (though maybe I've just
missed this happening in the past). This is a bug fix, that we'll want
in the next back branch updates, not just 9.3. Sticking it in the open
commit fest means it may well not get looked at for 2-3 months or so.
How do we prevent that happening?

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Boszormenyi Zoltan 2012-06-19 08:44:35 Re: [PATCH] lock_timeout and common SIGALRM framework
Previous Message Fabien COELHO 2012-06-19 08:31:09 Re: Pg default's verbosity?