From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
Cc: | Bernd Helmle <mailings(at)oopsware(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Materialized View patch broke pg_dump |
Date: | 2013-03-11 15:43:18 |
Message-ID: | 513DFB96.40805@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 03/11/2013 10:43 AM, Andrew Dunstan wrote:
>
> On 03/06/2013 10:55 AM, Kevin Grittner wrote:
>> Bernd Helmle <mailings(at)oopsware(dot)de> wrote:
>>
>>> Looking into this issue, it seems the version check in getTables()
>>> of pg_dump.c
>>> is wrong. Shouldn't the check be
>>>
>>> if (fout->remoteVersion >= 90300)
>>> {
>>>
>>> }
>>>
>>> since this is where pg_relation_is_scannable() is introduced?
>> Fixed.
>>
>> Thanks for the report!
>>
>>
>
>
>
> I noticed this morning that I am still getting failures on 9.0, 9.1
> and 9.2 which cause my cross-version upgrade testing to fail for git
> tip. For all I know this might apply to all back branches, but these
> are the only ones tested for upgrade, so that's all I can report on
> reliably.
>
> I'm chasing it up to find out exactly what's going on, but figured
> some extra eyeballs would help.
>
>
The problem is that pg_dump is sending an empty query in versions less
than 9.3, and choking on that. Suggested fix attached - there's really
no reason to be doing anything re mat views in versions < 9.3.
cheers
andrew
Attachment | Content-Type | Size |
---|---|---|
matviewdumpfix.patch | text/x-patch | 3.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-03-11 16:01:01 | Re: matview join view error |
Previous Message | Craig Ringer | 2013-03-11 14:51:21 | Re: Reproducible "Bus error" in 9.2.3 during database dump restoration (Ubuntu Server 12.04 LTS) |