On 01/21/2013 08:45 PM, Tom Lane wrote:
Stefan Kaltenbrunner writes:
On 01/21/2013 02:00 PM, Tom Lane wrote:
(It's entirely likely that the 7.0 server I keep around for testing this
is the last one in captivity anywhere. But IIRC, we've heard fairly
recent reports of people still using 7.2.
Stefan Kaltenbrunner writes:
> On 01/21/2013 02:00 PM, Tom Lane wrote:
>> (It's entirely likely that the 7.0 server I keep around for testing this
>> is the last one in captivity anywhere. But IIRC, we've heard fairly
>> recent reports of people still using 7.2. We'd have to desupport before
>>
On 01/21/2013 02:00 PM, Tom Lane wrote:
> Pavan Deolasee writes:
>> On Sun, Jan 20, 2013 at 4:29 AM, Tom Lane wrote:
>>> As submitted, this broke pg_dump for dumping from pre-8.0 servers.
>>> (7.4 didn't accept commas in SET TRANSACTION syntax, and versions
>>> before that didn't have the READ ON
On Mon, Jan 21, 2013 at 8:00 AM, Tom Lane wrote:
> Pavan Deolasee writes:
>> On Sun, Jan 20, 2013 at 4:29 AM, Tom Lane wrote:
>>> As submitted, this broke pg_dump for dumping from pre-8.0 servers.
>>> (7.4 didn't accept commas in SET TRANSACTION syntax, and versions
>>> before that didn't have t
Pavan Deolasee writes:
> On Sun, Jan 20, 2013 at 4:29 AM, Tom Lane wrote:
>> As submitted, this broke pg_dump for dumping from pre-8.0 servers.
>> (7.4 didn't accept commas in SET TRANSACTION syntax, and versions
>> before that didn't have the READ ONLY option at all.)
> My bad. I did not realiz
On Sun, Jan 20, 2013 at 4:29 AM, Tom Lane wrote:
> Pavan Deolasee writes:
>> Sorry for posting on such an old thread. But here is a patch that
>> fixes this. I'm also adding to the next commitfest so that we don't
>> lose track of it again.
>
> As submitted, this broke pg_dump for dumping from pr
Pavan Deolasee writes:
> Sorry for posting on such an old thread. But here is a patch that
> fixes this. I'm also adding to the next commitfest so that we don't
> lose track of it again.
As submitted, this broke pg_dump for dumping from pre-8.0 servers.
(7.4 didn't accept commas in SET TRANSACTIO
On Wed, Jan 16, 2013 at 1:21 AM, Pavan Deolasee wrote:
>
>
> On Wed, Jan 9, 2013 at 6:42 AM, Gurjeet Singh wrote:
>
>>
>>>
>> I have updated the commitfest submission to link to the correct patch
>> email.
>>
>>
> Thanks Gurjeet.
>
>
>> I initially thought that this patch deserves accompanying do
On Wed, Jan 9, 2013 at 6:42 AM, Gurjeet Singh wrote:
>
>>
> I have updated the commitfest submission to link to the correct patch
> email.
>
>
Thanks Gurjeet.
> I initially thought that this patch deserves accompanying documentation
> because pg_dump's serializable transaction may error out beca
On Mon, Dec 31, 2012 at 1:38 AM, Pavan Deolasee wrote:
> On Sun, Dec 30, 2012 at 12:38 AM, Stephen Frost
> wrote:
> > * Pavan Deolasee (pavan.deola...@gmail.com) wrote:
> >> On Fri, Sep 7, 2012 at 6:06 PM, Kevin Grittner
> >> > That makes sense to me. The reason I didn't make that change when I
On Sun, Dec 30, 2012 at 12:38 AM, Stephen Frost wrote:
> * Pavan Deolasee (pavan.deola...@gmail.com) wrote:
>> On Fri, Sep 7, 2012 at 6:06 PM, Kevin Grittner
>> > That makes sense to me. The reason I didn't make that change when I
>> > added the serializable special case to pg_dump was that it se
* Pavan Deolasee (pavan.deola...@gmail.com) wrote:
> On Fri, Sep 7, 2012 at 6:06 PM, Kevin Grittner
> > That makes sense to me. The reason I didn't make that change when I
> > added the serializable special case to pg_dump was that it seemed
> > like a separate question; I didn't want to complicat
On Mon, Sep 10, 2012 at 10:00 PM, Pavan Deolasee
wrote:
> On Fri, Sep 7, 2012 at 6:06 PM, Kevin Grittner
> wrote:
>
>
>> That makes sense to me. The reason I didn't make that change when I
>> added the serializable special case to pg_dump was that it seemed
>> like a separate question; I didn't
On Fri, Sep 7, 2012 at 6:06 PM, Kevin Grittner
wrote:
> That makes sense to me. The reason I didn't make that change when I
> added the serializable special case to pg_dump was that it seemed
> like a separate question; I didn't want to complicate an already big
> patch with unnecessary changes
Pavan Deolasee wrote:
> I'm looking at the following code in pg_dump.c
>
> /*
>* Start transaction-snapshot mode transaction to dump
>* consistent data.
>*/
> ExecuteSqlStatement(fout, "BEGIN");
> if (fout->remoteVersion >= 90100)
> {
> if (serializable_deferrable)
>
I'm looking at the following code in pg_dump.c
/*
* Start transaction-snapshot mode transaction to dump consistent data.
*/
ExecuteSqlStatement(fout, "BEGIN");
if (fout->remoteVersion >= 90100)
{
if (serializable_deferrable)
ExecuteSqlStatement(fout,
16 matches
Mail list logo
