Postgres Complete backup

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Postgres Complete backup

Sridhara KB
Hi,

How can i take postgres complete backup including users schema triggers etc…..

P.S currently running postgres 9.4


Thanks,
Sridhara K.b
Reply | Threaded
Open this post in threaded view
|

Re: Postgres Complete backup

Ron-2
On 1/30/19 12:19 AM, Sridhara KB wrote:
> Hi,
>
> How can i take postgres complete backup including users schema triggers etc…..
>
> P.S currently running postgres 9.4

https://www.postgresql.org/docs/9.6/app-pgdump.html


--
Angular momentum makes the world go 'round.

Reply | Threaded
Open this post in threaded view
|

Re: Postgres Complete backup

Shreeyansh dba
In reply to this post by Sridhara KB
You can go with pg_dumpall or pg_basebackup.

Thanks & Regards,
Shreeyansh DBA Team
www.shreeyansh.com


On Wed, Jan 30, 2019 at 11:49 AM Sridhara KB <[hidden email]> wrote:
Hi,

How can i take postgres complete backup including users schema triggers etc…..

P.S currently running postgres 9.4


Thanks,
Sridhara K.b
Reply | Threaded
Open this post in threaded view
|

Re: Postgres Complete backup

Sridhara KB
In reply to this post by Ron-2
Hi

Have gone through this url, but  size of pgdata of old database and pgdata of new database are not matching.
Basically am doing migration activity from one instance pgsql9.4 to other instance pgsql 9.4

 

> On 30-Jan-2019, at 11:55 AM, Ron <[hidden email]> wrote:
>
> On 1/30/19 12:19 AM, Sridhara KB wrote:
>> Hi,
>>
>> How can i take postgres complete backup including users schema triggers etc…..
>>
>> P.S currently running postgres 9.4
>
> https://www.postgresql.org/docs/9.6/app-pgdump.html
>
>
> --
> Angular momentum makes the world go 'round.
>


Reply | Threaded
Open this post in threaded view
|

Re: Postgres Complete backup

Tom Lane-2
Sridhara KB <[hidden email]> writes:
> Have gone through this url, but  size of pgdata of old database and pgdata of new database are not matching.

That in itself means nothing.

A freshly-reloaded table will contain no dead space, and freshly-rebuilt
indexes typically have less bloat than ones that have been used for
awhile.  So the fact that your new database is smaller per "du" does
not mean you lost data.

                        regards, tom lane