I am terribly sorry. I was sinked in this for about 2 days and just a
few minutes after i posted this a was told by a 3rd person that I am
using datbase postgres instead of eb3_nz to searched for pending OID in
pg_rewrite. So the common delete from pg_rewrite where oid = 1001837 worked.
Thanks a lo
On 03/14/2014 06:56 AM, Jakub Can wrote:
Hello, our database suddenly went broken somehow. We still dont know if
it is becouse of hw failure etc., anyway, when I try to make dump using
pg_dump or pg_dumpall I have got error message like this:
pg_dump: failed sanity check, parent table OID 100183
Is your table really named "blob" ??? You said it fails when it gets to the
table named "blob" not somewhere in the process of dumping the table
"blob"...
There might be a clue in that... What happens if yo rename the table to
something other than an SQL reserverd word ?
Although postgreSQL doe
"Carlos Oliva" <[EMAIL PROTECTED]> writes:
> We are getting the following error message whe we run "pg_dump -Ft name> > database.tar":
> pg_dump: ERROR: canceling query due to user request
This implies that something sent SIGINT to the backend process.
We've heard some reports that suggest tha
Tom Lane wrote:
"Jimmie H. Apsey" <[EMAIL PROTECTED]> writes:
At this point, I am unable to do a pg_dump using our new Rec Hat
Enterprise Linux AS 4 version of Postgres which is version 7.4.
Here's what I get when I try to do a pg_dump of our database:
[ ~]$ /usr/bin/pg_dump dcf_2005040
"Jimmie H. Apsey" <[EMAIL PROTECTED]> writes:
> At this point, I am unable to do a pg_dump using our new Rec Hat
> Enterprise Linux AS 4 version of Postgres which is version 7.4.
> Here's what I get when I try to do a pg_dump of our database:
> [ ~]$ /usr/bin/pg_dump dcf_20050404 >& /~/dcf_200504
"Jimmie H. Apsey" <[EMAIL PROTECTED]> writes:
> This may be my second posting but I think I've done it correctly this time.
> At this point, I am unable to do a pg_dump using our new Rec Hat
> Enterprise Linux AS 4 version of Postgres which is version 7.4.
> Here's what I get when I try to do a pg
What I was trying to do was export the database on one computer and import it onto another. I gave up trying to fix the export problem since I had an old backup of the database. It was old enough that it was short three tables, but I have the raw tab delimited data so I just reconstructed the datab
On Tue, 19 Apr 2005 11:53 pm, Lorenzo Thurman wrote:
> Thanks for the reply. I've tried recompiling with my install build
> settings, but no luck. I've posted a message on the Gentoo forums.
> Hopefully they will have an answer. If they do, I'll post back here for
> future reference.
>
I read y
Thanks for the reply. I've tried recompiling with my install build
settings, but no luck. I've posted a message on the Gentoo forums.
Hopefully they will have an answer. If they do, I'll post back here for
future reference.
On Apr 19, 2005, at 1:01 AM, Tom Lane wrote:
Lorenzo Thurman <[EMAIL PR
Lorenzo Thurman <[EMAIL PROTECTED]> writes:
> I'm trying that right now. I think there may be mis-match in the build
> settings between upgrades of postgresql. The "USE" settings may be at
> fault:
> - - pg-hier: Enables recursive queries like Oracle's 'CONNECT
> BY' feature.
[ rolls
I'm trying that right now. I think there may be mis-match in the build settings between upgrades of postgresql. The "USE" settings may be at fault:
- - pg-hier: Enables recursive queries like Oracle's 'CONNECT BY' feature.
- - pg-vacuumdelay : Adds in the vacuum inter-page delay feature.
-
Lorenzo Thurman <[EMAIL PROTECTED]> writes:
>>> ERROR: did not find '}' at end of input node
> I installed this from Gento's portage repository.
Gentoo has a history of supplying broken compilers, software, etc
... bleeding edge stuff tends to cut you occasionally :-(
You might try updating you
On Apr 18, 2005, at 4:46 p, Tom Lane wrote:
Also, does "select * from pg_user" provoke the same error in every
database of your installation, or only this one? If the latter,
it could be a data-corruption kind of problem.
I only have one database right now. When I try "select * from pg_user", I
Lorenzo Thurman <[EMAIL PROTECTED]> writes:
> 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_databa
> "SE" == Sarah Ewen <[EMAIL PROTECTED]> writes:
SE> Hi there folks,
SE> I've just had pg_dump fail on me for the first time ever, and I'm not
SE> sure why.
SE> It generates 24MB of dump before bombing out with:
SE> pg_dump: socket not open
SE> pg_dump: SQL command to dump the contents of ta
Sarah Ewen <[EMAIL PROTECTED]> writes:
>> Is this repeatable? What shows up in the postmaster's log when it
>> happens? What platform is this on, and what version of Postgres?
> This is postgresql-7.4.6-1.FC2.2 running on RedHat Fedora Core 2.
> The logs don't reveal anything, and it happens co
Hi there Tom, thanks for your reply.
pg_dump: socket not open
pg_dump: SQL command to dump the contents of table "activity_log"
failed: PQendcopy() failed.
pg_dump: Error message from server: socket not open
pg_dump: The command was: COPY public.activity_log (
TO stdout
Is this repeatable? What
Sarah Ewen <[EMAIL PROTECTED]> writes:
> I've just had pg_dump fail on me for the first time ever, and I'm not
> sure why.
> It generates 24MB of dump before bombing out with:
> pg_dump: socket not open
> pg_dump: SQL command to dump the contents of table "activity_log"
> failed: PQendcopy() fai
19 matches
Mail list logo
