Re: Old problem needs solution

From: Alvaro Herrera <alvherre(at)surnet(dot)cl>
To: "Gerald D(dot) Anderson" <gander(at)vte(dot)com>
Cc: Russell Smith <mr-russ(at)pws(dot)com(dot)au>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: Old problem needs solution
Date: 2005-06-03 23:25:02
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-general

On Fri, Jun 03, 2005 at 05:55:36PM -0500, Gerald D. Anderson wrote:
> Ok, you're over my head now so I'm just going to post the results in the
> hope that something clicks. Here ya go:

Ok, I diff'ed both and guess what:

("a" is your output, "b" is mine)

07:19 drizzt ~ 0$ diff a b
< :limitCount <> :hierClause <> :setOperations <> :resultRelations ()})
> :limitCount <> :setOperations <> :resultRelations ()})

So we now have confirmed that the problem is the hierarchical queries

> That help? *cringe*

I guess your build with the "use flag" wasn't successful. I think you
have two choices:

1. really build with the patch installed, and dump your data using that

2. Make an update of pg_rewrite in order to get rid of that. I think
this is easier, but you should be very careful not to corrupt the table.
I'd start by doing a CREATE TABLE AS to copy the contents of pg_rewrite
somewhere else, just in case you screw it up. Then come up with some
clever UPDATE query to remove the extraneous ":hierClause <> " part.

Alvaro Herrera (<alvherre[a]>)
"In Europe they call me Niklaus Wirth; in the US they call me Nickel's worth.
That's because in Europe they call me by name, and in the US by value!"

In response to


Browse pgsql-general by date

  From Date Subject
Next Message Gerald D. Anderson 2005-06-04 00:02:16 Re: Old problem needs solution
Previous Message Scott Marlowe 2005-06-03 23:23:28 Re: Autonomous Transactions