Postgres

[Chris Hughes]

Hi all thanks for your help.

Took a copy of the pg_dump and pg_dumpall out of the folder
/usr/pgsql-9.5/bin

and placed in the /usr/bin/

Works fine now.


Chris Hughes

Copious Data Pty Ltd (Trading as Atad Data)
Unit 8 /3460 Pacific Highway
Springwood QLD 4127
Phone No:- 07 3208 6347
Mobile No:- 0409 263 349
Fax No:- 07 3208 9347
Email:- ataddata at bigpond.net.au
Web Site:- http://ataddata.com.au



-----Original Message-----
From: omnisdev-en [mailto:omnisdev-en-bounces at lists.omnis-dev.com] On Behalf
Of Doug Easterbrook
Sent: Monday, 31 July 2017 11:01 PM
To: OmnisDev List - English
Subject: Re: Postgres

hi Mark:

just to correct a misconception..  pg_dump works absolutely fine whether
there area users logged in or not.


it uses a feature called MVCC (multi version concurrency Control) to ensure
that a pg_dump that is started has absolute logical consistency.   so you
can fire of pg_dumps any time you want through a day while people a re using
the database and it will be a perfect snapshot of the data at that instant
in time.

https://www.postgresql.org/docs/current/static/mvcc-intro.html



the problem with server mismatch is that newer versions of pg_dump are
backward compatible.   Older versions are not forward compatible, in case
there have been changes to variable types, extensions and what have you.

so to get a dump of an older database, best thing is to get the most recent
pg_dump.     as another lister pointed out, pgadmin4 has a copy.    or
installing the latest postgres server will create a copy in the bin
directory that you can take elsewhere.







Doug Easterbrook
Arts Management Systems Ltd.
mailto:doug at artsman.com
http://www.artsman.com
Phone (403) 650-1978

> On Jul 30, 2017, at 10:31 PM, Mark Phillips <mark.phillips at mophilly.com>
wrote:
> 
> It may be that there are users logged. Pg_dump assumes no logged on users.
> 
> Hth,
> 
> - Mark Phillips
> 
>> On Jul 30, 2017, at 8:12 PM, Chris Hughes <ataddata at bigpond.net.au>
wrote:
>> 
>> Hi All
>> 
>> 
>> 
>> I know it's not a Omnis problem.
>> 
>> 
>> 
>> This is the error message I get using a Centos 7 system. It was 
>> suppose to be the latest 9.5 Postgresql, when I try using the PGadmin3.
>> 
>> 
>> 
>> Start Error message.
>> 
>> 
>> 
>> usr/bin/pg_dump --host 127.0.0.1 --port 5432 --username "atad" 
>> --no-password --format custom --blobs --verbose --file 
>> "/home/centos2/general_office/FastTrackSQLBackup/monday20170731.backup"
>> "deofficesql001"
>> 
>> pg_dump: server version: 9.5.7; pg_dump version: 9.2.18
>> 
>> pg_dump: aborting because of server version mismatch
>> 
>> 
>> 
>> Process returned exit code 1.
>> 
>> End Error message.
>> 
>> 
>> 
>> I did a complete install and so assumed that the dump version would 
>> be the same.
>> 
>> 
>> 
>> 
>> 
>> Chris Hughes
>> 
>> 
>> 
>> Copious Data Pty Ltd (Trading as Atad Data)
>> 
>> Unit 8 /3460 Pacific Highway
>> 
>> Springwood QLD 4127
>> 
>> Phone No:- 07 3208 6347
>> 
>> Mobile No:- 0409 263 349
>> 
>> Fax No:- 07 3208 9347
>> 
>> Email:- ataddata at bigpond.net.au
>> 
>> Web Site:- http://ataddata.com.au
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _____________________________________________________________
>> Manage your list subscriptions at http://lists.omnis-dev.com
> 
> 
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com