SEO

Greetings!

At some point, I'm not even sure when, I apparently had a bad upgrade on
one of my production databases. I'm in a situation now where I've got
my back up against a wall and not sure what to do. The problem is, I'm
receiving this message frequently:

did not find '}' at end of input node

I am currently running version 7.4.7 and am trying to migrate on up to
8. The data is completely available to the application (large forums
database is primary concern), but I can't back it up or do anything with
it aside from let it dig itself deeper.

Does anybody have a suggestion on how to fix this, or some way around
it? I could probably write a script to suck all my data out and push it
back in, but I'm hoping and praying there's something better out there,
hopefully a real honest to goodness fix for it ; )

Thanks,

G


---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

Gerald D. Anderson wrote:
> Greetings!
>
> At some point, I'm not even sure when, I apparently had a bad upgrade on
> one of my production databases. I'm in a situation now where I've got
> my back up against a wall and not sure what to do. The problem is, I'm
> receiving this message frequently:
>
> did not find '}' at end of input node

When?

> I am currently running version 7.4.7 and am trying to migrate on up to
> 8. The data is completely available to the application (large forums
> database is primary concern), but I can't back it up or do anything with
> it aside from let it dig itself deeper.

Can you pg_dump individual tables (with -t my_table_name)

--
Richard Huxton
Archonet Ltd

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

data # pg_dump -Fc -f blah.txt -tforums_auth forums22 -u
User name: postgres
Password:
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: did not find '}' at end of
input node
pg_dump: The command was: SELECT (SELECT usename FROM pg_user WHERE
usesysid = datdba) as dba, pg_encoding_to_char(encoding) as encoding,
datpath FROM pg_database WHERE datname = 'forums22'

That help? As far as when, pretty much anytime I do anything. My guess
is messed up metadata.

G


Richard Huxton wrote:

> Gerald D. Anderson wrote:
>
>> Greetings!
>>
>> At some point, I'm not even sure when, I apparently had a bad upgrade
>> on one of my production databases. I'm in a situation now where I've
>> got my back up against a wall and not sure what to do. The problem
>> is, I'm receiving this message frequently:
>>
>> did not find '}' at end of input node
>
>
> When?
>
>> I am currently running version 7.4.7 and am trying to migrate on up
>> to 8. The data is completely available to the application (large
>> forums database is primary concern), but I can't back it up or do
>> anything with it aside from let it dig itself deeper.
>
>
> Can you pg_dump individual tables (with -t my_table_name)
>

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

On Wed, Jun 01, 2005 at 10:24:25AM -0500, Gerald D. Anderson wrote:
> Greetings!
>
> At some point, I'm not even sure when, I apparently had a bad upgrade on
> one of my production databases. I'm in a situation now where I've got
> my back up against a wall and not sure what to do. The problem is, I'm
> receiving this message frequently:
>
> did not find '}' at end of input node

Are you using Gentoo? Are you using the hierarchical queries patch?
Were you using any of the above in the previous Postgres version?

If this is the case, you will have to get the old postmaster again, and
run it against your data directory, and use that to make the dump. The
reload it in the new directory.

The problem with the hierarchical queries patch (which Gentoo applies to
some of their builds) is that it doesn't include the necessary
catalog-version increment. So people can use the same data directory
with or without the patch applied, which is a mistake because it causes
the errors you are seeing.

--
Alvaro Herrera (<alvherre[a]surnet.cl>)
"Use it up, wear it out, make it do, or do without"

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Gerald D. Anderson wrote:
> data # pg_dump -Fc -f blah.txt -tforums_auth forums22 -u User
> name: postgres
> Password:
> pg_dump: SQL command failed
> pg_dump: Error message from server: ERROR: did not find '}' at end of
> input node
> pg_dump: The command was: SELECT (SELECT usename FROM pg_user WHERE
> usesysid = datdba) as dba, pg_encoding_to_char(encoding) as encoding,
> datpath FROM pg_database WHERE datname = 'forums22'
>
> That help? As far as when, pretty much anytime I do anything. My guess
> is messed up metadata.

Yep - I'm guessing it's an issue with an array (group membership?) in
pg_user.

Can you SELECT * FROM pg_user?
--
Richard Huxton
Archonet Ltd

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Richard Huxton <dev@archonet.com> writes:
> Yep - I'm guessing it's an issue with an array (group membership?) in
> pg_user.

No, I'll bet lunch that Alvaro fingered the correct culprit: either
addition or subtraction of that darn hierarchical-query patch. It
changes the on-disk representation of view rules in a way that produces
exactly this failure mode.

One of the disadvantages of open source is that you can't prevent people
from breaking your software :-(

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Ok, well it looks like Richard owes Tom a lunch, or that's my best guess
anyway. I am running Gentoo, as far as that particular patch, I'm
unsure, but if it's installed by default then yes. So, I've pulled down
the earliest ebuild I can get which is 7.3.6. Get it installed and go
to start it:

FATAL: The data directory was initialized by PostgreSQL version 7.4,
which is not compatible with this version 7.3.6.

So, the plot thickens. Is there somewhere I can go tweak a few bytes to
make it think it's 7.3? Also, is 7.3 going to be early enough? This
database has been around for years, and like I said, I'm not sure when
this happened : /

Truly appreciate the help guys!

g



Alvaro Herrera wrote:

>On Wed, Jun 01, 2005 at 10:24:25AM -0500, Gerald D. Anderson wrote:
>
>
>>Greetings!
>>
>>At some point, I'm not even sure when, I apparently had a bad upgrade on
>>one of my production databases. I'm in a situation now where I've got
>>my back up against a wall and not sure what to do. The problem is, I'm
>>receiving this message frequently:
>>
>>did not find '}' at end of input node
>>
>>
>
>Are you using Gentoo? Are you using the hierarchical queries patch?
>Were you using any of the above in the previous Postgres version?
>
>If this is the case, you will have to get the old postmaster again, and
>run it against your data directory, and use that to make the dump. The
>reload it in the new directory.
>
>The problem with the hierarchical queries patch (which Gentoo applies to
>some of their builds) is that it doesn't include the necessary
>catalog-version increment. So people can use the same data directory
>with or without the patch applied, which is a mistake because it causes
>the errors you are seeing.
>
>
>

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

"Gerald D. Anderson" <gander@vte.com> writes:
> So, the plot thickens. Is there somewhere I can go tweak a few bytes to
> make it think it's 7.3?

No. That's not what you want anyway; you want a late 7.4 build, just
one without the hierarchical-queries patch. I dunno enough about Gentoo
to say how you get rid of a patch you don't want, but if it's anything
like RPMs, you can just dike the patch out of the specfile and rebuild.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

On Fri, 3 Jun 2005 12:38 am, Tom Lane wrote:
> "Gerald D. Anderson" <gander@vte.com> writes:
> > So, the plot thickens. Is there somewhere I can go tweak a few bytes to
> > make it think it's 7.3?
>
> No. That's not what you want anyway; you want a late 7.4 build, just
> one without the hierarchical-queries patch. I dunno enough about Gentoo
> to say how you get rid of a patch you don't want, but if it's anything
> like RPMs, you can just dike the patch out of the specfile and rebuild.
>
USE="-pg-hier" emerge -vp =postgresql-7.4.7-r2

Will do the job on gentoo. It's not enabled by default unless somebody has put
pg-hier somewhere in the use flags.

Regards

Russell Smith



> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>
>

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Yup, was just going to respond this morning. It isn't enabled by
default (at least in the ebuilds I've looked at). I've built it with
pg_hier and without pg_hier and get the same results either way : /
Might there be some other cause for this? Or even a dirty fix if this
is what it is?

Gerald


Russell Smith wrote:

>On Fri, 3 Jun 2005 12:38 am, Tom Lane wrote:
>
>
>>"Gerald D. Anderson" <gander@vte.com> writes:
>>
>>
>>>So, the plot thickens. Is there somewhere I can go tweak a few bytes to
>>>make it think it's 7.3?
>>>
>>>
>>No. That's not what you want anyway; you want a late 7.4 build, just
>>one without the hierarchical-queries patch. I dunno enough about Gentoo
>>to say how you get rid of a patch you don't want, but if it's anything
>>like RPMs, you can just dike the patch out of the specfile and rebuild.
>>
>>
>>
>USE="-pg-hier" emerge -vp =postgresql-7.4.7-r2
>
>Will do the job on gentoo. It's not enabled by default unless somebody has put
>pg-hier somewhere in the use flags.
>
>Regards
>
>Russell Smith
>
>
>
>
>
>> regards, tom lane
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 9: the planner will ignore your desire to choose an index scan if your
>> joining column's datatypes do not match
>>
>>
>>
>>
>
>
>

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly