Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] [badalex@gmail.com: Re: [BUGS] Problem identifying constraints which should not be inherited]

From: "Alex Hunsaker" <badalex(at)gmail(dot)com>
To: NikhilS <nikkhils(at)gmail(dot)com>
Cc: "Pg Patches" <pgsql-patches(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] [badalex@gmail.com: Re: [BUGS] Problem identifying constraints which should not be inherited]
Date: 2008-04-01 02:03:14
Message-ID: 34d269d40803311903y3c508c84k9f0eb856412eadd6@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On Mon, Mar 31, 2008 at 2:36 AM, NikhilS <nikkhils(at)gmail(dot)com> wrote:
> Hi Alex,

> I was taking a look at this patch to add the pg_dump related changes. Just
> wanted to give you a heads up as this patch crashes if we run "make
> installcheck". Seems there is an issue introduced in the CREATE TABLE
> REFERENCES code path due to your patch (this is without my pg_dump changes
> just to be sure).  Looks like some memory overwrite issue. The trace is as
> follows:

Ouch, sorry i did not reply sooner... been out with the flu.  Oddly
enough make check and make installcheck worked great on my 64 bit box.
 But on my laptop(32 bits) make check lights up like a christmas tree.
 Which is why I did not notice the problem. :(

Attached is a patch that fixes the problem... (it was debugging from
an earlier version)

Attachment: fix.patch
Description: text/x-diff (547 bytes)

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2008-04-01 02:12:06
Subject: Re: How embarrassing: optimization of a one-shot query doesn't work
Previous:From: Tom LaneDate: 2008-04-01 01:51:08
Subject: Re: How embarrassing: optimization of a one-shot query doesn't work

pgsql-patches by date

Next:From: Tom LaneDate: 2008-04-01 04:58:44
Subject: Re: Consistent \d commands in psql
Previous:From: Gregory StarkDate: 2008-03-31 21:51:09
Subject: Re: Consistent \d commands in psql

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group