Re: [GENERAL] pgdump

On 30/01/2015 14:46, Adrian Klaver wrote: > On 01/30/2015 01:16 AM, Ramesh T wrote: >> when i try to dump the database windows based pgadmin 3 it returns >> message like >> >> pg_dump: server version: 9.3.4; pg_dump version: 9.1.3 >> pg_dump: aborting because of server version mismatch >> >> any he

Re: [GENERAL] pgdump

On 01/30/2015 01:16 AM, Ramesh T wrote: when i try to dump the database windows based pgadmin 3 it returns message like pg_dump: server version: 9.3.4; pg_dump version: 9.1.3 pg_dump: aborting because of server version mismatch any help..? Use a 9.3+ version of pg_dump. A version of pg_dump i

Re: [GENERAL] pgdump (9.2.4) not dumping all tables

Marcos Cano wrote: [missing data after dump/restore of DB with PostGIS] > i found this in the file... > > ERROR: could not access file "$libdir/rtpostgis-2.0": No such file or > directory Could it be that PostGIS was not installed as an extension in the old database, so that the dump contains th

Re: [GENERAL] pgdump (9.2.4) not dumping all tables

so i fix it and got it working !!! i followed the best practices of doing the dump with the newest pg_dump version. and now is working thanks everyone for your help -- View this message in context: http://postgresql.nabble.com/pgdump-9-2-4-not-dumping-all-tables-tp5827736p5827821.html Sent fr

Re: [GENERAL] pgdump (9.2.4) not dumping all tables

On Thu, 20 Nov 2014 11:52:23 -0700 (MST) Marcos Cano wrote: > i found this in the file... > > ERROR: could not access file "$libdir/rtpostgis-2.0": No such file or > directory > > > which acording to the firs link I found >

Re: [GENERAL] pgdump (9.2.4) not dumping all tables

yes i'd better look at the postgis list.. i thought for one moment that this was encoding related. thanks for your help -- View this message in context: http://postgresql.nabble.com/pgdump-9-2-4-not-dumping-all-tables-tp5827736p5827760.html Sent from the PostgreSQL - general mailing list archi

Re: [GENERAL] pgdump (9.2.4) not dumping all tables

On 11/20/2014 10:52 AM, Marcos Cano wrote: i found this in the file... What file? Remember the list need context for your statements. You are at the computer and see all that goes on. We only know what you tell us and statements without supporting data are hard to troubleshoot. ERROR: c

Re: [GENERAL] pgdump (9.2.4) not dumping all tables

i found this in the file... ERROR: could not access file "$libdir/rtpostgis-2.0": No such file or directory which acording to the firs link I found , is a postgis

Re: [GENERAL] pgdump (9.2.4) not dumping all tables

On Thu, 20 Nov 2014 11:25:10 -0700 (MST) Marcos Cano wrote: > i did it again... and the file shows exactly the same lots of : > > invalid command \N > invalid command \N > invalid command \N > invalid command \N > invalid command \N > invalid command \N > invalid command \N > invalid command \N

Re: [GENERAL] pgdump (9.2.4) not dumping all tables

to answer to Adrian 1) i am using the old version to dump (i will try with the latest) 2) no the postgis version is different. pg9.2.4-> postgis-2.0.3 and pg9.3.5-> postgis-2.1.3 3) the schema is public \d+ al_shared_place Table "pu

Re: [GENERAL] pgdump (9.2.4) not dumping all tables

i did it again... and the file shows exactly the same lots of : invalid command \N invalid command \N invalid command \N invalid command \N invalid command \N invalid command \N invalid command \N invalid command \N -- View this message in context: http://postgresql.nabble.com/pgdump-9-2-4-no

Re: [GENERAL] pgdump (9.2.4) not dumping all tables

On 11/20/2014 10:06 AM, Marcos Cano wrote: might be awkard but there is no file, so i assume 2 things: 1) there was no upgrade errors 2) the script + command is not writing to stderr (i think it is doing it) Aah, meant to add: Is there anything in the Postgres log for the time period of the re

Re: [GENERAL] pgdump (9.2.4) not dumping all tables

On 11/20/2014 10:06 AM, Marcos Cano wrote: might be awkard but there is no file, so i assume 2 things: 1) there was no upgrade errors So to be clear the file below does not exist?: 2>$backup_path/$db_upgrade_errors.txt" or it exists but there is nothing in it? 2) the script + command is

Re: [GENERAL] pgdump (9.2.4) not dumping all tables

On 11/20/2014 09:47 AM, Marcos Cano wrote: hello im trying to dump a complete DB, i've been doing something like this. (i'm in the process of upgrading from 9.2.4 to 9.3.5) my current DB looks like this: Name| Owner | Encoding | Collate | Ctype | Access privileges ---+-

Re: [GENERAL] pgdump (9.2.4) not dumping all tables

might be awkard but there is no file, so i assume 2 things: 1) there was no upgrade errors 2) the script + command is not writing to stderr (i think it is doing it) -- View this message in context: http://postgresql.nabble.com/pgdump-9-2-4-not-dumping-all-tables-tp5827736p5827739.html Sent

Re: [GENERAL] pgdump (9.2.4) not dumping all tables

Marcos Cano writes: > everything seems to work fine until i noticed that i'm missing 5 tables, Did you look at the error output from the restore to see if there were any complaints? regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org)

Re: [GENERAL] pgdump error "Could not open file pg_clog/0B8E: No such file or directory"

On Thu, Apr 25, 2013 at 5:13 AM, wrote: > Sorry for the delay. > No it does not exist. > > ls -l /var/lib/pgsql/data/pg_clog/0B8E > ls: /var/lib/pgsql/data/pg_clog/0B8E: No such file or directory > > Have 92 files in directory which are all 262144 in size. This file records if transactions commi

Re: [GENERAL] pgdump error "Could not open file pg_clog/0B8E: No such file or directory"

Sorry for the delay. No it does not exist. ls -l /var/lib/pgsql/data/pg_clog/0B8E ls: /var/lib/pgsql/data/pg_clog/0B8E: No such file or directory Have 92 files in directory which are all 262144 in size. On Wed, Apr 24, 2013 at 9:23 AM, Adrian Klaver wrote: > On 04/24/2013 03:35 AM, jesse.wat.

Re: [GENERAL] pgdump error "Could not open file pg_clog/0B8E: No such file or directory"

On 04/24/2013 03:35 AM, jesse.wat...@gmail.com wrote: I am receiving an error when running a pg_dump. These are older legacy systems and upgrading them is not in plan. Any help will be appreciated. CentOS 5.3 (64bit) psql (PostgreSQL) 8.3.11 full error message: pg_dump: SQL command failed

Re: [GENERAL] Pgdump error "invalid page header in block"

On Mar 4, 2011, at 1:17 PM, tuanhoanganh wrote: > pg_dump: reading dependency data > pg_dump: SQL command failed > pg_dump: Error message from server: ERROR: invalid page header in block 299 > of relation "pg_depend_depender_index" > pg_dump: The command was: SELECT classid, objid, refclassid,

Re: [GENERAL] Pgdump error "invalid page header in block"

On 03/03/11 11:47 PM, tuanhoanganh wrote: Yesterday, I had some problem with postgresql 9.0.2. Today i backup postgres and has error pg_dump: reading dependency data pg_dump: SQL command failed pg_dump: Error message from server: ERROR: invalid page header in block 299 of relation "pg_depend_

Re: [GENERAL] pgdump problem or question?

On Wed, Sep 10, 2008 at 3:31 PM, Bayless Kirtley <[EMAIL PROTECTED]> wrote: > Early Friday morning a bad record caused me to reload the Thursday night > pgdump backup. I performed a pgdump first to study later. In the backup I > found several incomplete transactions all done at the end of the day.

Re: [GENERAL] pgdump from 8.0.4 not valid for import into 8.1.0

Thanks Richard. Backup as compressed worked. Richard Huxton wrote: Richard Sydney-Smith wrote: ? In pgAdminIII linked to 8.0.4 server did a backup of all databased. Chose "plain" and saved to disk. uninstalled 8.0.4 installed 8.1.0 create database in pgAdminIII v1.4 restore reports as

Re: [GENERAL] pgdump from 8.0.4 not valid for import into 8.1.0

Richard Sydney-Smith wrote: ? In pgAdminIII linked to 8.0.4 server did a backup of all databased. Chose "plain" and saved to disk. uninstalled 8.0.4 installed 8.1.0 create database in pgAdminIII v1.4 restore reports as not a valid archive. Obviously this is not what I expect. Some older b

Re: [GENERAL] pgdump of schema...

Actually this database has been carried forward since the "postgres95" days, so you are definitely right in your analysis.. Would another (perhaps safer?) way of doing this is to remove the "CREATE SEQUENCE" and "SELECT pg_catalog.setval", and replace the "DEFAULT nextval" with "SERIAL" then rest

Re: [GENERAL] pgdump of schema...

"Net Virtual Mailing Lists" <[EMAIL PROTECTED]> writes: > When I do a "pgdump --schema=someschema somedatabase > something.dump", > the results of the dump file look like this: > CREATE TABLE emailtemplates ( > email_template_id integer DEFAULT > nextval('"emailtemplate_email_templat_seq"'::te

Re: [GENERAL] pgdump, large objects and 7.0->7.1

Philip Crotwell <[EMAIL PROTECTED]> writes: > So, 3 questions that basically boil down to "What is the best way to move > large objects from 7.0 to 7.1." > 1) Can I use the 7.1 pgdumpall to dump a 7.0.3 database? The docs say no, > but worth a try. The docs say no, and they mean no. There is a

Re: [GENERAL] pgdump

On Tue, Sep 19, 2000 at 09:15:32AM +0200, Andreas Tille wrote: > if I do a database dump via pg_dump also PostgreSQL internal tables > named pga_* are stored in the dump. However if I drop a database and pga_* are not really internal tables. The internal tables are named pg_*. pga_* are tables c

Re: [GENERAL] pgdump & blob

At 10:56 13/07/00 GMT+1, Alexandre FLAMENT wrote: >Is there a version of pg_dump that save blob ? There is pg_dump_lo in contrib/ and there is an experimental version available for testing at: ftp://ftp.rhyme.com.au/pub/postgresql/pg_dump/blobs/ ---