From: | Andy Hartman <hartman60home(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Backup |
Date: | 2024-10-23 17:43:02 |
Message-ID: | CAEZv3coqKQdiNFvLKE=-aiT9VYzzhvrjBr_UC0Z0smYfaHoM+A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm using the DB as a History repository... I'm pulling info from a Mssql
db using a P/S script to a csv file then Import that to Postgres I only
keep 6 months live on the mssql db and roll everything else to Postgres
Arch DB.
After I load this latest month to Postgres I just need to backup, or
should I just retain my .csv files as a Backup... I have 2 tables that I
load to Hist and one table holds the images...
THanks .
On Wed, Oct 23, 2024 at 11:50 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 10/23/24 07:07, Andy Hartman wrote:
> > I have been testing different backup methods suggested and wonder if I
> > have all my files used to load the DB .. could that be considered a
> > backup... obviously need to have schema backup in case of problem, but
> > that seems to be easily re-created
> >
> > Thoughts?
>
> Did you actually read the information at the links provided?
>
> By default pg_dump and pg_dumpall will dump both the schema definitions
> as well as the data.
>
> Yes it is a backup of the database(s) at the point in time you initiate
> the dump. If you want something different then you are probably looking
> for one of the replication methods. You still have not answered:
>
> " You also need to provide a more detailed description of what you want
> the backup to do?"
>
> so it is hard to say what method is best for your situation.
>
> >
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2024-10-23 19:47:01 | Re: Backup |
Previous Message | Tom Lane | 2024-10-23 16:04:30 | Re: Using Expanded Objects other than Arrays from plpgsql |