.
Sincerely,
Kasia
From: McKinzie, Alan (Alan) [mailto:alan...@avaya.com]
Sent: Tuesday, May 21, 2013 5:05 AM
To: Craig James; Kasia Tuszynska
Cc: pgsql-admin@postgresql.org
Subject: RE: [ADMIN] pg_restore
Does your database restore happen to perform a "Drop owned by" command as part
of t
gresql.org
[mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Craig James
Sent: Monday, May 20, 2013 7:45 PM
To: Kasia Tuszynska
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_restore
On Mon, May 20, 2013 at 3:57 PM, Kasia Tuszynska
mailto:ktuszyn...@esri.com>> wrote:
Hi Every
On Mon, May 20, 2013 at 3:57 PM, Kasia Tuszynska wrote:
> Hi Everybody,
>
> Has anyone ran into issues running pg_restore?
>
> It seems that between 8.3.8 and 9.0.5, 9.1.3 the behavior of pg_restore
> has changed.
>
> ** **
>
> Previously I was able to have several data owners with
Hi Everybody,
Has anyone ran into issues running pg_restore?
It seems that between 8.3.8 and 9.0.5, 9.1.3 the behavior of pg_restore has
changed.
Previously I was able to have several data owners with their own schemas and
running a pg_restore as one superuser was able to restore the objects in
[copying the list; please keep the list copied on all replies]
Ramana Panda wrote:
> I am using the Version : *"PostgreSQL 8.0.0 on i686-pc-mingw32,
> compiled by GCC gcc.exe (GCC) 3.4.2 (mingw-special)"*
You didn't even keep up on bug fix releases? It's amazing that your
database is still r
"ramana.pls" wrote:
> I am getting an error while restoring the Database Backup. I am
> postgre sql 8.0 with Windows XP O.S.
PostgreSQL version 8.0 has been out of support overall for years,
and out of support for Windows for years before that.
http://archives.postgresql.org/pgsql-announce/2
"ramana.pls" writes:
> I am getting an error while restoring the Database Backup. I am postgre sql
> 8.0 with Windows XP O.S.
8.0? You do know that's been out of support for several years now,
right?
> while restoring the data i am getting
> pg_restore: [custom archiver] found unexpected block
Hi ,
I am getting an error while restoring the Database Backup. I am postgre sql
8.0 with Windows XP O.S.
while restoring the data i am getting
pg_restore: [custom archiver] found unexpected block ID (0) when reading
data --
expected 4034
Plz provide any solution.
Thanks in advance
--
Vi
Hi,
I don't know if this is a known problem, or something I'm doing wrong,
but pg_restore -j tends to sometimes mix lines, or even completely
drop some. Here is an example (it's a -j12 run):
pg_restore: pg_restore: restoring data for table
"edw_iu_paglac_axe1_kpi_lac_month_bh"
restoring data fo
Ravi,
To (attempt to) answer your questions:
1) does the custom archive format of pg_dump needs to be in a file (not
pipe) for the pg_restore to seek back &forth ?
Not to my knowledge.
I suspect that the windows "type" command is adding extra "header"
information to the file before
command is absolutely perfect, it seems that windows doesn't
> like the form sometimes.
>
> M
>
> -Original Message-
> From: pgsql-admin-ow...@postgresql.org
> [mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Kevin Grittner
> Sent: 29 March 2011 18:41
&g
[mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Kevin Grittner
Sent: 29 March 2011 18:41
To: Ravi Thati; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_restore on windows with pipe
Ravi Thati wrote:
> type C:\testdump | pg_restore -Fc [...]
> pg_restore: [custom archiver] *cou
Ravi Thati wrote:
> type C:\testdump | pg_restore -Fc [...]
> pg_restore: [custom archiver] *could not find block ID 1770* in
> archive -- possibly corrupt archive
> pg_restore: *** aborted because of error
Does the type command treat the stream as characters? (You could
try putting a ^Z en
Hi All,
I am trying to restore a dump (custom archive format) using pg_restore like
this:
type C:\testdump | pg_restore -Fc -C -U postgres -w -d postgres
where testdump contains the database dump from the following commmand:
pg_dump -U postgres -Fc test > C:\testdump
*the restore command fai
On Tue, Apr 20, 2010 at 11:32 AM, Tom Lane wrote:
> There was something similar reported here:
> http://archives.postgresql.org/pgsql-admin/2010-04/msg00237.php
> but we haven't got to the bottom of it yet.
That issue turned out to be me not paying attention to the pg_dump
output. There was a de
Scott Mead writes:
> On Wed, Apr 14, 2010 at 2:38 AM, Justin Falk wrote:
>> This results in an error:
>> pg_restore: [custom archiver] dumping a specific TOC data block out of
>> order not supported without ID on this input stream (fseek required)
> I'm pretty sure that you need to use the 8.4 v
On Wed, Apr 14, 2010 at 12:38 AM, Justin Falk wrote:
> Hi,
>
> I'm trying to use the -j option on pg_restore while restoring a database
> into PG 8.4.3.
>
> The dump was executed on PG 8.3.7 (Windows, Server 2003) using:
I think you have to dump with 8.4 to use -j on restore.
--
Sent via pgsql-
Justin Falk wrote:
> I'm trying to use the -j option on pg_restore while restoring a
> database into PG 8.4.3.
>
> The dump was executed on PG 8.3.7 (Windows, Server 2003) using:
Using the 8.4.3 version of pg_dump, as recommended in the
documentation?:
http://www.postgresql.org/docs/8.4/int
On Wed, Apr 14, 2010 at 2:38 AM, Justin Falk wrote:
> Hi,
>
> I'm trying to use the -j option on pg_restore while restoring a database
> into PG 8.4.3.
>
> The dump was executed on PG 8.3.7 (Windows, Server 2003) using:
>
> pg_dump -Fc -U postgres mydb > mydb.backup
>
> This results in a ~3.4 GB
Justin Falk writes:
> When I try to restore I'm using:
> pg_restore -d mydb -U postgres -j 4 mydb.backup
> This results in an error:
> pg_restore: [custom archiver] dumping a specific TOC data block out of order
> not supported without ID on this input stream (fseek required)
There was something
Justin Falk wrote:
> Hi,
>
> I'm trying to use the -j option on pg_restore while restoring a database
> into PG 8.4.3.
>
> The dump was executed on PG 8.3.7 (Windows, Server 2003) using:
>
> pg_dump -Fc -U postgres mydb > mydb.backup
>
> This results in a ~3.4 GB dump file.
>
> When I try to r
Hi,
I'm trying to use the -j option on pg_restore while restoring a database
into PG 8.4.3.
The dump was executed on PG 8.3.7 (Windows, Server 2003) using:
pg_dump -Fc -U postgres mydb > mydb.backup
This results in a ~3.4 GB dump file.
When I try to restore I'm using:
pg_restore -d mydb -U po
On Sat, Apr 17, 2010 at 5:53 PM, Steve Crawford
wrote:
> Bryan White wrote:
>>
>> ...
>> The new server is a dual socket Nahalem. 8 cores, 16 threads, 48 GB
>> ram, 2 WAL drives in RAID1 and 12 database drives in RAID10.
>>
>
> I would try setting -j higher - in your case try 8 for starters. Also
Bryan White wrote:
...
The new server is a dual socket Nahalem. 8 cores, 16 threads, 48 GB
ram, 2 WAL drives in RAID1 and 12 database drives in RAID10.
I would try setting -j higher - in your case try 8 for starters. Also
turn off fsync and autovacuum (and turn them back on !!!). See these a
> It was unclear from your email how you are creating the dump. Did you create
> the dump with the 8.1 or the 8.4 version of pg_dump? When upgrading, the
> docs recommend using the newer version of the dump utility: "It is
> recommended that you use the pg_dump and pg_dumpall programs from the newe
On Sat, Apr 17, 2010 at 2:46 PM, Tom Lane wrote:
> Bryan White writes:
>> I get this error:
>> pg_restore: [custom archiver] dumping a specific TOC data block out of
>> order is not supported without ID on this input stream (fseek
>> required)
>
> I can't duplicate that here using latest 8.1.x pg
Bryan White writes:
> I get this error:
> pg_restore: [custom archiver] dumping a specific TOC data block out of
> order is not supported without ID on this input stream (fseek
> required)
I can't duplicate that here using latest 8.1.x pg_dump and 8.4.x
pg_restore ... what versions are you using
Bryan White wrote:
I am trying to load a data base using pg_restore.. Is there a known
problem with using parallel
loading in 8.4 from a file created with an 8.1 database?
It was unclear from your email how you are creating the dump. Did you
create the dump with the 8.1 or the 8.4 ver
I am trying to load a data base using pg_restore. We are migrating to
a new server and I want to see if I can make the load go faster if I
load with pg_restore instead of psql.
The old server is:
CentOS upgraded to 5.4 64bit with the stock PostgreSQL 8.1.
The dump file was created with:
pg_d
admin@postgresql.org
Subject: Re: [ADMIN] pg_restore : change schema
Julio Leyva writes:
> What about alter schema ?
How would that help?
If I understand correctly, the original poster is trying to do something
like:
Source DB
schema1.table1
And restore it to
schema2.table1
--
Sent via pgsql-admin
Julio Leyva writes:
What about alter schema ?
How would that help?
If I understand correctly, the original poster is trying to do something
like:
Source DB
schema1.table1
And restore it to
schema2.table1
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes
Christophe Dore writes:
Imagine I have used pg_dump to backup a given single schema.
Is there any feature in pg_restore (8.4) that would allow to restore this
schema in a schema with another name ?
I think there isn't. If the pg_dump is ASCII and the file is small enough
you could edit it.
Hi
Imagine I have used pg_dump to backup a given single schema.
Is there any feature in pg_restore (8.4) that would allow to restore this
schema in a schema with another name ?
Thanks
--
Christophe Doré
on. I have included the log of the pg_dump
> and restore.
>
> Best regards:
>
> Baubak
>
>
>
> -Original Message-
> From: Ian Lea [mailto:ian@gmail.com]
> Sent: mardi 1 décembre 2009 18:31
> To: Baubak Gandomi
> Cc: pgsql-admin@postgresql.org
> Su
You could start by saying what version of postgres, on what OS, and
posting your backup and restore commands with any output, error or
otherwise, that they produce.
--
Ian.
On Tue, Dec 1, 2009 at 4:48 PM, Baubak Gandomi
wrote:
> Hello,
>
>
>
> I have a problem restoring a database. I have mad
Hello,
I have a problem restoring a database. I have made a dump of a schema,
with no error messages. When I restore my dump I do not get any error
messages either. But when I look into my schema I see that I have less
tables than before. I don't even know how to debug this problem !
Best r
Hello everybody,
I am using postgres 8.0 on a server that I use for
testing, G4 with 2 cpu x 2.8 Ghz and 4 GB ram, so I've dump data of the
production server into testing one, I have the problem after the restore, I
found that don't restore the index and triggers, but everythin
Hi All,
I am facing an error on executing the below command
dump name: pg_dump_FcZ0.pnps_200903041201_1.2.1.0_base_testing
databae name: pnqd_test
$pg_restore -U postgres -p 5433 -d pnqd_test
pg_dump_FcZ0.pnps_200903041201_1.2.1.0_base_testing
pg_restore: [archiver (db)] Error while PROCESSING
Dear All,
I am having a backup file in tar format. While restoring it through
pg_restore instantly i am getting an following error.
*Command - pg_restore -d cipa
/cipa/RAJASTHAN/RAJASTHAN/CIPABACKUP01_08_2008.TAR
Error - pg_restore: [archiver] out of memory
*I have increased shmmax , maintenace
ED]>; pgsql-admin@postgresql.org
> Sent: Monday, 19 May, 2008 1:05:03 AM
> Subject: Re: [ADMIN] pg_restore test procedures (a bit OT)
>
> > I was just wondering if anyone has any clever way of testing their backups
> taken with pg_dump on a daily basis?
> I have a daily ba
> I was just wondering if anyone has any clever way of testing their backups
taken with pg_dump on a daily basis?
I have a daily bash script to backup of one of my databases to file, then
file to tape, which I test restore once per week. I've changed some of my
variables to hard-coded strings to ma
Hi chaps,
I was just wondering if anyone has any clever way of testing their backups
taken with pg_dump on a daily basis?
On a slightly separate note,
I've setup a daily restore onto a staging server that I intend to also use to
test the dumps, at the moment I've just set up a cron job. I'm su
I¹m attempting to do something that should be a trivially simple task. I
want to do a data only dump from my production data in the public schema and
restore it on another machine. Both machines are running 8.2.5, both
machines are virtually identical and have 16GB of RAM.
I created an archive w
I agree that they ³should². Unfortunately, nothing about slony is simple,
in my experience.
On 3/19/08 3:17 PM, "Tom Lane" <[EMAIL PROTECTED]> wrote:
> Aaron Brown <[EMAIL PROTECTED]> writes:
>> > Yes, it kind of needs to be data only since I am pulling from a slonized
>> > database. My exper
Aaron Brown <[EMAIL PROTECTED]> writes:
> Yes, it kind of needs to be data only since I am pulling from a slonized
> database. My experience has been if you don¹t load the schema first with a
> schema from slony1_extract_schema.sh, we end up with all the slony triggers
> and crap in the dump. If
Yes, it kind of needs to be data only since I am pulling from a slonized
database. My experience has been if you don¹t load the schema first with a
schema from slony1_extract_schema.sh, we end up with all the slony triggers
and crap in the dump. If there is a better way of doing this, I¹m
definit
Aaron Brown <[EMAIL PROTECTED]> writes:
> I¹m attempting to do something that should be a trivially simple task. I
> want to do a data only dump from my production data in the public schema and
> restore it on another machine.
Does it really need to be data-only? A regular schema+data dump usual
I¹m attempting to do something that should be a trivially simple task. I
want to do a data only dump from my production data in the public schema and
restore it on another machine. Both machines are running 8.2.5, both
machines are virtually identical and have 16GB of RAM.
I created an archive w
Kevin Kempter <[EMAIL PROTECTED]> writes:
> Trying to restore a pg_dump I get this:
> pg_restore: ERROR: invalid byte sequence for encoding "UTF8": 0xae
> HINT: This error can also happen if the byte sequence does not match the
> encoding expected by the server, which is controlled by "client_en
> Trying to restore a pg_dump I get this:
>
> pg_restore: ERROR: invalid byte sequence for encoding "UTF8": 0xae
> HINT: This error can also happen if the byte sequence does not match the
> encoding expected by the server, which is controlled by "client_encoding".
> CONTEXT: COPY imm_lookup, li
Hi List;
Trying to restore a pg_dump I get this:
pg_restore: ERROR: invalid byte sequence for encoding "UTF8": 0xae
HINT: This error can also happen if the byte sequence does not match the
encoding expected by the server, which is controlled by "client_encoding".
CONTEXT: COPY imm_lookup, lin
On Dec 13, 2007 10:06 PM, Kevin Kempter <[EMAIL PROTECTED]> wrote:
> Hi list;
>
> We're seeing this error whern trying to restore a pg_dump file:
>
>
> -
> pg_restore: ERROR: invalid byte seque
Am Donnerstag, 13. Dezember 2007 18.06:23 schrieb Kevin Kempter:
> Hi list;
>
> We're seeing this error whern trying to restore a pg_dump file:
>
> ---
>-- pg_restore: ERROR: invalid byte sequence f
Hi list;
We're seeing this error whern trying to restore a pg_dump file:
-
pg_restore: ERROR: invalid byte sequence for encoding "UTF8": 0x9f CONTEXT:
COPY log_customer_api, line 4551 pg_res
Hi ALL,
I am trying to restore 2G dump file using pg_restore and it will erros
out with the following message;
pg_restore: [custom archiver] could not uncompress data: too many length
or distance symbol". Has anyone seen this before? I 'd really appreciate
your help.
Thanks,
Dinesh
--
After running pg_dumpall on my database cluster like this:
$PGBIN/pg_dumpall -c -U ipscdb | gzip > /var/db/pgsql_bkp/pg_dump_file.gz
I subsequently delete the PGDATA directory for the backed up database and
initialize a new database. Next I attempt to run the restore using
initialized data
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Colton A Smith wrote:
>> I have a 90G postgis-enabled postgresql
>> database that I'm upgrading from 8.1.5 to
>> 8.2.1. I initiated pg_restore nearly
>> six days ago and it's still churning away,
>> surely but slowly. Is this amount of
>> time norma
Colton A Smith wrote:
> Hi:
>
> I have a 90G postgis-enabled postgresql
> database that I'm upgrading from 8.1.5 to
> 8.2.1. I initiated pg_restore nearly
> six days ago and it's still churning away,
> surely but slowly. Is this amount of
> time normal? Or have I done something
> wrong?
6 day
Hi:
I have a 90G postgis-enabled postgresql
database that I'm upgrading from 8.1.5 to
8.2.1. I initiated pg_restore nearly
six days ago and it's still churning away,
surely but slowly. Is this amount of
time normal? Or have I done something
wrong?
Any help is appreciated!
Thanks
--
"Shahryar G. Hashemi" <[EMAIL PROTECTED]> writes:
> pg_restore: creating ACL trig_account_password_insert()
> pg_restore: [archiver (db)] could not execute query: ERROR: zero-length
> delimited identifier at or near at character 60
Since 8.0, pg_dump/pg_restore have been careful to include t
Hello,
We are running PostgreSQL 7.4.7 on a Linux system. We have a primary DB
and hot-standby [via pg_dump/pg_restore]. A few weeks ago we had a
database corruption and had to go back to a dump from 12/20/2006.
Everything restored fine [on the primary and standby DB's] however
everytime we per
=?ISO-8859-1?Q?Lu=EDs_Sousa?= <[EMAIL PROTECTED]> writes:
> Steps to reproduce:
> 1. pg_dump with -Fc option from database
> 2. A column name on table C is changed
> 3. pg_restore using option -S and --disable-triggers with error
> identifying that a column on table C was changed
> 4. drop table B
Hi again,
Version: 7.4.7-6sarge3
Structure of database: table A (id_a primary key) <-> table B (id_a,id_c
- foreign keys from table A and table C) <-> table C (id_c primary key).
Table A, table B and table C have one record for test purposes
Problem: After error on pg_restore can't drop table
Hi,
Is it possible to do a pg_restore inside a block transaction? That is,
if something goes wrong on restore all data can be rolled back.
Thanks
Luís Sousa
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Thanks AaronI am trying to do exactly the same thing. Now that my understanding of pg_restore is clearer. I was worried by my index key table was corrupted somehow and caused the error message. This is the cause by my own misunderstanding.CYAaron Bono <[EMAIL PROTECTED]> wrote: I agree. When rest
I agree. When restoring a database from back up, I do a drop database and recreate it to make sure everything is properly intact (tables, columns, views, triggers, foreign keys, etc...). We do this a lot for testing. We backup the production database, copy to test server and do a restore on the
Infor Gates <[EMAIL PROTECTED]> writes:
> I am having the impression that pg_restore would over-rides the "old"
> data with the current one. Is my thinking wrong?
Yeah. By default, pg_restore will issue a CREATE TABLE (which of course
fails if the table already exists) followed by COPY (which jus
Dear TomThanks for your email.You are right in saying table is already populated with the data. I was testing the pg_dump and pg_restore using pg_Admin III. I am having the impression that pg_restore would over-rides the "old"data with the current one. Is my thinking wrong? I have checked thedocum
Infor Gates <[EMAIL PROTECTED]> writes:
> I hope you could help me understand the error message below:
> While it looks straight forward, I could NOT find the duplicate key violation,
Considering that it's complaining at the very first line of COPY data,
I wonder whether you aren't restoring into
Dear listI hope you could help me understand the error message below:While it looks straight forward, I could NOT find the duplicate key violation,even though check through the said table (transaction by transaction). So,I am wondering if the message would means something else.I had tried re-indexi
I am using pgAdmin and phpPgAdmin with the same results (no triggers, no indexes).Thanks but the docs were not helpful yet. I've been trying to solve the issue many times in the past few monthes before posting to the list today.
:(On 27 Apr 2006 07:45:55 -0400, Jerry Sievers <[EMAIL PROTECTED]> wro
"David Levy" <[EMAIL PROTECTED]> writes:
> So I am trying to restore a pg_dump (version8.1 ) sql dump file from
> a remote 8.0.3 DB into a local 8.1 DB using pg_restore (version
> 8.1). Is there something incompatible The dump file seems to be
> correct regarding index creation statements I really
Hi, I am having troubles using pg_restore : none of my indexes are restored !It did not see any relevant message in the pg_restore output to explain this behaviour.So I am trying to restore a pg_dump (
version8.1
) sql dump file from a remote 8.0.3 DB into a local 8.1 DB using pg_restore (version 8
Hi, I am having troubles using pg_restore : none of my indexes are restored !It did not see any relevant message in the pg_restore output to explain this behaviour.So I am trying to restore a pg_dump (version8.1
) sql dump file from a remote 8.0.3 DB into a local 8.1 DB using pg_restore (version 8.
[Please copy the mailing list on replies.]
On Mon, Dec 12, 2005 at 11:57:06AM -0500, Josh O'Brien wrote:
> this is the command --create --format=c -d template1
> /home/postgres/dumps/test_dump test_db.
That's not a complete command; I assume those are the options and
arguments to pg_restore. As
On Mon, Dec 12, 2005 at 10:23:09AM -0500, Josh O'Brien wrote:
> I'm trying to restore in a cluster using pg_restore and i'm receiving an
> error from my recoverylog saying that there is no last checkpoint for my
> backend. How can I alter pg_restore to make it work or do i have any
> other opti
Hello all
I'm trying to restore in a cluster using pg_restore and i'm receiving an
error from my recoverylog saying that there is no last checkpoint for my
backend. How can I alter pg_restore to make it work or do i have any
other options. Tahnk you in advance.
begin:vcard
fn:Joshua O'Brien
On 16.09.2005 07:31, Victor Sudakov wrote:
Is there any way to fix or workaround this except editing the dump with a text
editor (very frustrating with dozens of objects in several schemas being out of
order)?
In case you only have a text dump.. uhm.. No.
In case it's a binary dump, using a n
D Kavan wrote:
I do a full vacuum and analyze every night, but I'm getting this error.
Those aren't errors. They are letting you know that you need to increase
your checkpoint_segments.
chived transaction log file "000100120091"
< % %2005-08-12 06:13:49 EDT>LOG: archived transa
I do a full vacuum and analyze every night, but I'm getting this error.
chived transaction log file "000100120091"
< % %2005-08-12 06:13:49 EDT>LOG: archived transaction log file
"000100120092"
< % %2005-08-12 06:13:57 EDT>LOG: archived transaction log file
"000100
"D Kavan" <[EMAIL PROTECTED]> writes:
> That did the trick. 30 minutes only for a restrore instead of 5 + hours.
Good.
> I did notice that the size is 4 GB instead of 5.6 GB. Is something else
> going on?
Kinda sounds like you weren't vacuuming often enough in the old
installation, leading to
Thanks!
We increased work memory from 16 MB to 32 MB and maintenance work memory
from 256 MB to 768 MB. That made a huge difference. We did set true the
log.statement and duration, but where is the file those are logging too?
That did the trick. 30 minutes only for a restrore instead of 5
Bruno Wolff III <[EMAIL PROTECTED]> writes:
>> psql dbname < dump_file
>> pg_restore -d test_restore_2 -Fc niehs_dump.backup
> Some things you can do are to turn off fsync for the restore and not
> restore foreign key contsraints and indexes until after the database
> has been loaded.
pg_dump/pg_
On Thu, Aug 11, 2005 at 15:29:22 -0400,
D Kavan <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> We are running postgres 8.03.
>
> Getting a dump is no problem on our 6 GB database. However, the restore is
> a killer, it takes 10 minutes for the dump pg_dump, but over 5 hours for a
> restore. Is th
Hi all,
We are running postgres 8.03.
Getting a dump is no problem on our 6 GB database. However, the restore is
a killer, it takes 10 minutes for the dump pg_dump, but over 5 hours for a
restore. Is there a way to 'turn off transactions' on the restore to speed
things up? I've tried diff
rk always, but is
definitely a promising start.
Thanks a bunch!
Gopal.
> -Original Message-
> From: Chris Travers [mailto:[EMAIL PROTECTED]
> Sent: Saturday, July 16, 2005 3:35 AM
> To: Gopal Srinivasa; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_restore hangs
I don't have any experience on HP-UX so take this with a grain of salt...
Gopal Srinivasa wrote:
The 'funny' thing is that it works perfectly on some HP-UX systems and hangs
on some others. I've seen it happen on both IA and PA architectures. Also,
sometimes deleting some strings and restorin
Hi,
I am using PostgreSQL 7.4.2 on HP-UX systems. I am trying to pg_restore a
dump created using pg_dump with the following command-line:
pg_dump -Fc -fcerdump -Uemt -p10864 cer
The dump only has one table "emt_str", with integers and strings as its
attributes. Essentially, the table stores some
I am having an issue with postgres 7.3.4 and pg_restore.
I have a pg_dump archive that I made with the following command:
pg_dump -p -h -Fc -Z9 -f db.dmp -v
However, when I try to do a pg_restore for a specific table, it is not
restoring the permission to the table. Is there a way to have
pg_
EMAIL PROTECTED]>
(BCc: "Bruce Momjian" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
(BSent: Monday, November 01, 2004 2:56 PM
(BSubject: Re: [ADMIN] pg_restore TODO - delay PK creation
(B
(B
(B> "Iain" <[EMAIL PROTECTED]> writes:
(B>> IIRC
"Iain" <[EMAIL PROTECTED]> writes:
> IIRC there has been a bug fix to the COPY command, regarding handling
> backslashed Ns or something like that sometime between 7.1 and 7.4, if I
> dump the 7.1 db with the 7.4 version of pg_dump then do I get the fixes to
> COPY?
My recollection is that some
BTo: "Iain" <[EMAIL PROTECTED]>
(BCc: "Bruce Momjian" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
(BSent: Monday, November 01, 2004 12:36 PM
(BSubject: Re: [ADMIN] pg_restore TODO - delay PK creation
(B
(B
(B> "Iain" <[EMAIL PROTECTED]> wri
"Iain" <[EMAIL PROTECTED]> writes:
> Out of interest, what is the word on using newer versions of pg_dump on
> older verisons of the DB - is it is possible or even wise to unload a 7.1
> DB with the 7.4 version of pg?
Standard, recommended procedure is to use the later version of pg_dump
to unl
Iain wrote:
> Hi Bruce,
>
> OK, I've just looked into it and you are right, thanks.
>
> In the case I just tested I restored a 7.1 dump to a 7.4.6 db. I had assumed
> that this is a restore time issue but in fact it is dependent on the format
> of the dump file. I noticed the problem after the
;[EMAIL PROTECTED]>
Sent: Monday, November 01, 2004 11:36 AM
Subject: Re: [ADMIN] pg_restore TODO - delay PK creation
Iain wrote:
Hi,
I'm wondering if this is already on some todo list for pg_restore but I
didn't find any mention of it anywhere, so I thought I should post this
and
Iain wrote:
> Hi,
>
> I'm wondering if this is already on some todo list for pg_restore but I
> didn't find any mention of it anywhere, so I thought I should post this and
> see what people think..
>
> Basically, I'd like to see an option at restore time to not include the
> primary key constr
(B
(B
(BHi,
(B
(BI'm wondering if this is already on some
(Btodo list for pg_restore but I didn't find any mention of it anywhere, so I
(Bthought I should post this and see what people think..
(B
(BBasically, I'd like to see an option at
(Brestore time to not include the primary ke
, but a
stable production system should be relatively OK. Just my experience anyway.
regards
Iain
- Original Message -
From: "Lee Wu" <[EMAIL PROTECTED]>
To: "Düster Horst" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, October 30, 2004 1:39 AM
: Friday, October 29, 2004 7:52 AM
To: [EMAIL PROTECTED]
Subject: Re: [ADMIN] pg_restore error
OK, the manual talk about this solution, but I do have more than 2000
objects in my DB. What is the reason that pg_dump/pg_restore are not able to
create an correct order ob DB objects with respect to
OBS because the
> restauration of single objects will not restore BOLBS.
>
> Horst Düster
>
> -Ursprüngliche Nachricht-
> Von: Vishal Kashyap @ [Sai Hertz And Control Systems]
> [mailto:[EMAIL PROTECTED]
> Gesendet am: Freitag, 29. Oktober 2004 11:33
> An: Düs
1 - 100 of 229 matches
Mail list logo
