On Wed, Dec 6, 2017 at 9:52 PM, Martin Mueller <
martinmuel...@northwestern.edu> wrote:
>
>
> On 12/6/17, 4:39 AM, "karsten.hilb...@gmx.net"
> wrote:
>
> On Tue, Dec 05, 2017 at 09:52:28PM +, Martin Mueller wrote:
>
> > Are there rules for thumb for deciding when you can dump a
>
On Wed, Dec 6, 2017 at 7:52 AM, Martin Mueller <
martinmuel...@northwestern.edu> wrote:
>
> The objective is to create a backup from which I can restore any or all
> tables in the event of a crash. In my case, I use Postgres for my own
> scholarly purposes. Publications of whatever kind are not
John, all,
* John R Pierce (pie...@hogranch.com) wrote:
> On 12/5/2017 2:09 PM, Martin Mueller wrote:
> >Time is not really a problem for me, if we talk about hours rather
> >than days. On a roughly comparable machine I’ve made backups of
> >databases less than 10 GB, and it was a matter of minut
On Wed, Dec 06, 2017 at 12:52:53PM +, Martin Mueller wrote:
>> Are there rules for thumb for deciding when you can dump a
>> whole database and when you’d be better off dumping groups of
>> tables?
>> It seems to me we'd have to define the objective of "dumping" first ?
> The objective is to
On 12/6/17, 4:39 AM, "karsten.hilb...@gmx.net" wrote:
On Tue, Dec 05, 2017 at 09:52:28PM +, Martin Mueller wrote:
> Are there rules for thumb for deciding when you can dump a
> whole database and when you’d be better off dumping groups of
> tables?
It seems to
On Tue, Dec 05, 2017 at 09:52:28PM +, Martin Mueller wrote:
> Are there rules for thumb for deciding when you can dump a
> whole database and when you’d be better off dumping groups of
> tables?
It seems to me we'd have to define the objective of "dumping" first ?
Regards,
Karsten
--
GPG ke
Carl Karsten wrote:
> On Tue, Dec 5, 2017 at 4:15 PM, Alvaro Herrera
> wrote:
> > A backup generated by pg_dump never includes writes that are in flight
> > while the backup is being taken. That would make the backup absolutely
> > worthless!
>
> Hmm, i kinda glossed over my point:
> if you com
On 12/5/2017 2:09 PM, Martin Mueller wrote:
Time is not really a problem for me, if we talk about hours rather
than days. On a roughly comparable machine I’ve made backups of
databases less than 10 GB, and it was a matter of minutes. But I know
that there are scale problems. Sometimes program
On Tue, Dec 5, 2017 at 4:15 PM, Alvaro Herrera
wrote:
> Carl Karsten wrote:
> > Nothing wrong with lots of tables and data.
> >
> > Don't impose any constraints on your problem you don't need to.
> >
> > Like what are you backing up to?$400 for a 1T ssd or $80 fo a 2T usb3
> > spinny disk.
>
On Tue, Dec 5, 2017 at 3:09 PM, Martin Mueller <
martinmuel...@northwestern.edu> wrote:
> Time is not really a problem for me, if we talk about hours rather than
> days. On a roughly comparable machine I’ve made backups of databases less
> than 10 GB, and it was a matter of minutes. But I know t
Carl Karsten wrote:
> Nothing wrong with lots of tables and data.
>
> Don't impose any constraints on your problem you don't need to.
>
> Like what are you backing up to?$400 for a 1T ssd or $80 fo a 2T usb3
> spinny disk.
>
> If you are backing up while the db is being updated, you need to
To: Martin Mueller
Cc: "pgsql-general@lists.postgresql.org"
Subject: Re: a back up question
On Tue, Dec 5, 2017 at 2:52 PM, Martin Mueller
mailto:martinmuel...@northwestern.edu>> wrote:
Are there rules for thumb for deciding when you can dump a whole database and
when you’d be be
Nothing wrong with lots of tables and data.
Don't impose any constraints on your problem you don't need to.
Like what are you backing up to?$400 for a 1T ssd or $80 fo a 2T usb3
spinny disk.
If you are backing up while the db is being updated, you need to make sure
updates are queued until t
On Tue, Dec 5, 2017 at 2:52 PM, Martin Mueller <
martinmuel...@northwestern.edu> wrote:
> Are there rules for thumb for deciding when you can dump a whole database
> and when you’d be better off dumping groups of tables? I have a database
> that has around 100 tables, some of them quite large, and
14 matches
Mail list logo
