Tom,
That did the trick. I made a bad assumption that the shared_memory
was causing the problem and not the other way around. I set it up to
256, last attempt was 128 and it still failed, not sure what value
would have given me success (128 - 256) but it needed quite a bit
more.
Thanks for your
jtke...@verizon.net writes:
> I am having a problem running "pg_dump -s database "on one system
> while it runs fine on another system.
> when I run the following dump on the Ubuntu system I get :
> pg_dump -s DB >/tmp/DB_schema_only.dmp
> pg_dump: WARNING: out of shared memory
> pg_dump: SQL
I am having a problem running "pg_dump -s database "on one system
while it runs fine on another system.
Both databases are nearly identical (minor changes to schemas and
tables)
On the older system it is a redhat x.x (32 bit) 12GiB memory running
postgresql 8.4.3 (32 bit)
On the newer system it is
Kevin Grittner ha scritto:
Silvio Brandani wrote:
We have a standby database
During pg_dump
Hmm... I just noticed that word "standby" in there. Can you
elaborate on what you mean by that?
-Kevin
It means it is an istance refreshed (via rsync) from another istanc
Kevin Grittner ha scritto:
Silvio Brandani wrote:
We have a standby database
During pg_dump
Hmm... I just noticed that word "standby" in there. Can you
elaborate on what you mean by that?
-Kevin
It means it is an istance refreshed (via rsync) from another istanc
Silvio Brandani wrote:
> We have a standby database
> During pg_dump
Hmm... I just noticed that word "standby" in there. Can you
elaborate on what you mean by that?
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www
Silvio Brandani wrote:
> We have a standby database version postgres 8.3.1 on linux .
You should seriously consider upgrading to a more recent 8.3 bug fix
release. The most current is now 8.3.11. Please read this:
http://www.postgresql.org/support/versioning
There was a bug fix related t
We have a standby database version postgres 8.3.1 on linux .
During pg_dump we get the error:
-- pg_dump: SQL command failed
-- pg_dump: Error message from server: ERROR: missing chunk number 0
for toast value 254723406
-- pg_dump: The command was: COPY helpdesk.attachments_data (id,
filedata,
Στις Friday 23 April 2010 17:05:46 ο/η Tom Lane έγραψε:
> Achilleas Mantzios writes:
> > Then i did
>
> > # CREATE TABLE mail_entity2 AS SELECT * FROM mail_entity;
>
> > which went fine
>
> > but, for some crazy reason, pg_dump on mail_entity2 also results to an
> > error:
> > srv:~> pg_dump -
Achilleas Mantzios writes:
> Then i did
> # CREATE TABLE mail_entity2 AS SELECT * FROM mail_entity;
> which went fine
> but, for some crazy reason, pg_dump on mail_entity2 also results to an error:
> srv:~> pg_dump -t mail_entity2 > /dev/null
> pg_dump: SQL command failed
> pg_dump: Error messa
Hello,
just coming back from a rescue marathon on this remote server i was telling you.
As i said, the last problem was while doing a
pg_dump dynacom
(dynacom is my db'd name)
i kept getting
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: compressed data is corrupt
pg_du
Guys PLEASE help. I still with the problem.
I've asked about my problem in opensolaris zfs list and what that they say
...
Most likely this is an application corruption problem. With ZFS
checksums, it's not possible to have undetected corruption of this type.
Of course, it's possible there is
Roman Chervotkin escribió:
> Hi list.
>
> Do usual pg_dump today and have got an error.
>
> -
> pg_dump: SQL command failed
> pg_dump: Error message from server: ERROR: compressed data is corrupt
> pg_dump: The command was: COPY public.candidates (id, name, surname,
> mid_nam
Please help,
I cannot understand what should be done in order to fix the issue.
Any hint, I tried search and irc but found nothing useful yet.
On 5/30/07, Roman Chervotkin <[EMAIL PROTECTED]> wrote:
Do usual pg_dump today and have got an error.
-
pg_dump: SQL command fai
Hi list.
Do usual pg_dump today and have got an error.
-
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: compressed data is corrupt
pg_dump: The command was: COPY public.candidates (id, name, surname,
mid_name, compensation, created, birthday, updated,
Do usual pg_dump today and have got an error.
-
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: compressed data is corrupt
pg_dump: The command was: COPY public.candidates (id, name, surname,
mid_name, compensation, created, birthday, updated, creator_i
"Karthikeyan Sundaram" <[EMAIL PROTECTED]> writes:
>Thanks for your reply. No, I recently installed (fresh installation)
> from scratch.
Well, your pg_dump seems to be finding an older version of libpq.so from
somewhere. Check for a pre-existing postgresql package.
Karthikeyan Sundaram wrote:
> Hi,
>
> I am using 8.2.1 on my dev server.
>
> When I do a pg_dump, I am getting an error message.
>
> pg_dump -U postgres podcast -t channel
>
> pg_dump: symbol lookup error: pg_dump: undefined symbol: PQescapeStringConn
>
> How can I resolved this? What
Hi Joshua,
Thanks for your reply. No, I recently installed (fresh installation)
from scratch.
Regards
skarthi
From: "Joshua D. Drake" <[EMAIL PROTECTED]>
To: Karthikeyan Sundaram <[EMAIL PROTECTED]>
CC: pgsql-admin@postgresql.org, pgsql-sql@postgresql.org
Subjec
Hi,
I am using 8.2.1 on my dev server.
When I do a pg_dump, I am getting an error message.
pg_dump -U postgres podcast -t channel
pg_dump: symbol lookup error: pg_dump: undefined symbol: PQescapeStringConn
How can I resolved this? What may be the problem?
Because of this, I am no
--- Dilipkumar <[EMAIL PROTECTED]> wrote:
> Date: Thu, 06 Jul 2006 20:21:53 +0530
> From: Dilipkumar <[EMAIL PROTECTED]>
> To: manjula hettiarachchi <[EMAIL PROTECTED]>
> Subject: Re: [ADMIN] pg_dump error
>
> Hi,
>
> Or try to run vaccum sc
Hi,
If you are trying to take a table dump try using this
pd_dump databasename -t tablename
if you are taking in the same server done mention as localhost just
switch user as postgress and give the above command mentioned.
manjula hettiarachchi wrote:
Hello List
I am using postgresql 7.4.
Hello List
I am using postgresql 7.4.7 in a voip production
setup.
I have been using pg_dump -Fc for regular backing up.
Since yesterday i am getting the following error for
the command:
root# pg_dump -h 'localhost' voipdb -t voipcall -Fc -f
voipcall.bak
The error is :
pg_dump: ERROR: invalid
Hi,
Doing "pg_dump -h192.168.XXX.XXX -U USER -d DB_NAME -C >
/file/where/dump/is/stored "
I got this error :
---
pg_dump: SQL command failed
pg_dump: Error message from server: server closed the co
Hello,
I am running Postgresql 8.0 on a win3K machine. I launched a backup using
the pgAdmin III utility. I chose the TAR option with BLOBs. I received the
following messages:
pg_dump: dumping content of table face
pg_dump: (tar archiver) actual file length (-760496003) does not match
expect
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> To Tom: could this be caused by a WAL recovery that wrote a page image
> to the wrong table? I guess it is very unlikely because the CRC of the
> WAL record would likely not match, but it's an idea.
I don't see any reason to think that WAL recovery wou
> How many columns does that table have?
It has 77 columns. INSERTS are always done on both this table and the table
that had the toast table error within the same transaction if that matters?
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed
On Thu, Sep 08, 2005 at 04:26:16PM +0100, Adam Witney wrote:
> On 8/9/05 3:46 pm, "Tom Lane" <[EMAIL PROTECTED]> wrote:
>
> > Adam Witney <[EMAIL PROTECTED]> writes:
> >> Here you go
> >
> >> pg_filedump-3.0/pg_filedump -i -f -R 34318 34320 134401986.1
> >
> > Thanks. What it looks like to
On 8/9/05 3:46 pm, "Tom Lane" <[EMAIL PROTECTED]> wrote:
> Adam Witney <[EMAIL PROTECTED]> writes:
>> Here you go
>
>> pg_filedump-3.0/pg_filedump -i -f -R 34318 34320 134401986.1
>
> Thanks. What it looks like to me is that block 34320 (really 165392)
> is data from some other file altoget
Adam Witney <[EMAIL PROTECTED]> writes:
> Here you go
> pg_filedump-3.0/pg_filedump -i -f -R 34318 34320 134401986.1
Thanks. What it looks like to me is that block 34320 (really 165392)
is data from some other file altogether. It's evidently still Postgres
heap data, but instead of having 3
Adam Witney <[EMAIL PROTECTED]> writes:
> Ah thanks.
> pg_filedump-3.0/pg_filedump -R 34318 34320 134401986.1
Could we see this with -i -f options please? At this level of detail
there's nothing obviously wrong ...
regards, tom lane
---(end of
Adam Witney <[EMAIL PROTECTED]> writes:
> Unfortunately the pg_filedump you requested gives an error:
> Error: Premature end of file encountered.
> (there is a .1 file also for this table, do I have to stick the two together
> or something?)
Yeah. Each file contains 131072 pages, so the correct p
On 8/9/05 2:38 pm, "Alvaro Herrera" <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 08, 2005 at 10:32:41AM +0100, Adam Witney wrote:
>
>> Unfortunately the pg_filedump you requested gives an error:
>>
>> pg_filedump -R 165390 165392 134401986
>>
>> *
On Thu, Sep 08, 2005 at 10:32:41AM +0100, Adam Witney wrote:
> Unfortunately the pg_filedump you requested gives an error:
>
> pg_filedump -R 165390 165392 134401986
>
> ***
> * PostgreSQL File/Block Formatted Dump Utility - Version
On 7/9/05 6:12 pm, "Tom Lane" <[EMAIL PROTECTED]> wrote:
> I wrote
>> Adam Witney <[EMAIL PROTECTED]> writes:
>>> I think I have found the offending row in measured_bioassay_base... The
>>> entry in its toast table looks like this
>
>>> bugasbase2=# select chunk_id, chunk_seq, length(chunk_data)
I wrote
> Adam Witney <[EMAIL PROTECTED]> writes:
>> I think I have found the offending row in measured_bioassay_base... The
>> entry in its toast table looks like this
>> bugasbase2=# select chunk_id, chunk_seq, length(chunk_data) from
>> pg_toast.pg_toast_134401982 where chunk_id = 144391872;
>>
Adam Witney <[EMAIL PROTECTED]> writes:
> I think I have found the offending row in measured_bioassay_base... The
> entry in its toast table looks like this
> bugasbase2=# select chunk_id, chunk_seq, length(chunk_data) from
> pg_toast.pg_toast_134401982 where chunk_id = 144391872;
> chunk_id | c
Adam Witney <[EMAIL PROTECTED]> writes:
> Got that now Sorry but I am being dim... But where do I find the file to
> dump.. You want the index on pg_toast_134401982 right?
Right (if that's the toast table you identified for the problem table).
It's probably named pg_toast_134401982_index. Loo
Adam Witney <[EMAIL PROTECTED]> writes:
>> I would be interested to see "pg_filedump -i -f" output for the toast
>> table's index before you blow it away, if you have time for that.
> Yep I can run this Can't seem to locate pg_filedump though... Its not in
> contrib... Anyone know where it is
On 7/9/05 4:28 pm, "Tom Lane" <[EMAIL PROTECTED]> wrote:
> Adam Witney <[EMAIL PROTECTED]> writes:
>>> I would be interested to see "pg_filedump -i -f" output for the toast
>>> table's index before you blow it away, if you have time for that.
>
>> Yep I can run this Can't seem to locate pg_fi
> I would be interested to see "pg_filedump -i -f" output for the toast
> table's index before you blow it away, if you have time for that.
Yep I can run this Can't seem to locate pg_filedump though... Its not in
contrib... Anyone know where it is these days?
--
This message has been scann
On 7/9/05 10:50 am, "Adam Witney" <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I just ran into an error from pg_dump:
>
> /usr/local/pgsql/bin/pg_dump -F p my_db
>
> pg_dump: ERROR: unexpected chunk number 3292 (expected 5) for toast value
> 144391872
> pg_dump: SQL command to dump the contents of
On Wed, Sep 07, 2005 at 10:50:44AM +0100, Adam Witney wrote:
> pg_dump: ERROR: unexpected chunk number 3292 (expected 5) for toast value
> 144391872
> pg_dump: SQL command to dump the contents of table "measured_bioassay_base"
You might have a corrupted TOAST table. Have you had any hardware
pro
Adam Witney <[EMAIL PROTECTED]> writes:
> pg_dump: ERROR: unexpected chunk number 3292 (expected 5) for toast value
> 144391872
> pg_dump: SQL command to dump the contents of table "measured_bioassay_base"
> failed: PQendcopy() failed.
> Any ideas whats happened here?
If you're lucky, it's just
Hi,
I just ran into an error from pg_dump:
/usr/local/pgsql/bin/pg_dump -F p my_db
pg_dump: ERROR: unexpected chunk number 3292 (expected 5) for toast value
144391872
pg_dump: SQL command to dump the contents of table "measured_bioassay_base"
failed: PQendcopy() failed.
pg_dump: Error message
An idea only.
Ever try this?
select reltype from pg_class where relname='foo';
Then, delete the reltype from pg_class
To me goes fine.
Best wishes,
Guido
Nigel Bishop wrote:
Hi
I'm getting an error with pg_dump:
I'm using
pg_dump -v -C -U username database > ./dumpfile.dmp
and it errors with:
pg_du
"Nigel Bishop" <[EMAIL PROTECTED]> writes:
> pg_dump: Attempt to lock table "Foo" failed. ERROR: MySchema:
> permission denied
Looks like you need to grant yourself usage rights on the schema
"MySchema".
> If I try to drop this it errors saying the table foo doesn't exist.
Can't tell whether y
Hi
I'm getting an error with pg_dump:
I'm using
pg_dump -v -C -U username database > ./dumpfile.dmp
and it errors with:
pg_dump: saving database definition
pg_dump: reading namespaces
pg_dump: reading user-defined types
pg_dump: reading user-defined functions
pg_dump: reading user-defined aggr
86 this request. I've found my problem. It seems that Dell had an old
version (7.2.2) of PostgreSQL installed. It was using pg_dump from that
version instead of the new version.
The database dump worked great with the new version.
Dave
David C. Brown wrote:
I'm receiving an error from pg_d
"David C. Brown" <[EMAIL PROTECTED]> writes:
> It says that it's using pg_dump version 7.2.2. I'm not sure if that is
> the version that comes with 7.3.3, but PostgreSQL was compile fresh from
> source on the new machine. Where it got this version of
> pg_dump/pg_dumpall I'm unclear of.
Your
I'm receiving an error from pg_dumpall while trying to backup my
database. To explain, this database used to be 7.2.1 but we have
upgraded the server and I just used pg_dumpall and then reloaded that
data into the new system which runs on 7.3.3 The problem is I get an
error when using pg_dump
yes, it was a problem with the hard disk.
thanks & best regards
dimitri
--
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!
---(end of broadcast)---
TIP 7: don't forget to in
> Dimitri Nagiev <[EMAIL PROTECTED]> writes:
> > using pg_dump I get the following error message:
> > pg_dump: ERROR: cannot read block 1055 of summary: Input/output error
> > calls from psql give me similar trouble:
> > ERROR: cannot read block 1055 of summary: Interrupted system call
>
> > The
Dimitri Nagiev <[EMAIL PROTECTED]> writes:
> using pg_dump I get the following error message:
> pg_dump: ERROR: cannot read block 1055 of summary: Input/output error
> calls from psql give me similar trouble:
> ERROR: cannot read block 1055 of summary: Interrupted system call
> There's a good ba
Hi all,
using pg_dump I get the following error message:
pg_dump stats > stats.sql
pg_dump: ERROR: cannot read block 1055 of summary: Input/output error
pg_dump: lost synchronization with server, resetting connection
pg_dump: SQL command to dump the contents of table "summary" failed:
PQendcopy
Ferdinand Smit <[EMAIL PROTECTED]> writes:
> What does this mean ?!? Is this a corrupt database, a bug or has the pg_dump
> not enough memory ?
> $ pg_dump login | gzip > login.dump.gz
> pg_dump: ERROR: MemoryContextAlloc: invalid request size 4294967293
> pg_dump: lost synchronization with ser
Hi,
What does this mean ?!? Is this a corrupt database, a bug or has the pg_dump
not enough memory ?
And ... how can i solve this problem ?
$ pg_dump login | gzip > login.dump.gz
pg_dump: ERROR: MemoryContextAlloc: invalid request size 4294967293
pg_dump: lost synchronization with server, re
[EMAIL PROTECTED] (Srinivasa Rao Chava) writes:
> pg_dump: query to obtain procedure name for trigger
> "ins_extranet_cspm_bug" did not return exactly one result
The most likely bet is that there's no function at all that matches the
OID stored in the trigger. Have you done any deletion/recreati
On 25 Feb 2002, Srinivasa Rao Chava wrote:
> I have recently upgraded to postgresql 7.2.
> When I try to take backup with pg_dump, one of the database is
> generating
> the following error.
>
> pg_dump: query to obtain procedure name for trigger
> "ins_extranet_cspm_bug" did not return exactly on
I have recently upgraded to postgresql 7.2.
When I try to take backup with pg_dump, one of the database is
generating
the following error.
pg_dump: query to obtain procedure name for trigger
"ins_extranet_cspm_bug" did not return exactly one result
I checked the for the trigger "ins_extranet_cs
Hello,gurus
I find that u reply a topic about "Backend sent D message without prior
T"
problem on usenet, I think u can help me.
I'm new in PostgreSQL, I need to dump a table to another one, so I issue
the
pg_dump command.
but after I execute pg_dump -adt member db1 > /tmp/member.sq
Hello,
I am getting the following error when trying to use pg_dump:
***
pg_dump cymi > cymi.2000_04_16.dmp
FATAL 1: Memory exhausted in AllocSetAlloc()
PQendcopy: resetting connection
SQL query to dump the contents of Table 'cymi_de
62 matches
Mail list logo
