From: | Olivier Gautherot <ogautherot(at)gautherot(dot)net> |
---|---|
To: | stan <stanb(at)panix(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: backing up the data from a single table? |
Date: | 2019-09-13 14:44:01 |
Message-ID: | CAJ7S9TWQtRisLU2RPTfogiGZrVFi3_CEWCzR_pFP7GE==if30A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Stan,
El vie., 13 de septiembre de 2019 11:14, stan <stanb(at)panix(dot)com> escribió:
> My development methodology is to create scripts that init the db, and load
> test data, as I make changes.
>
> Now, I am starting to move toward a test instance with real data. The end
> user has provided "real" test data, n spreadsheets. I have the inputing of
> data from these working OK. (takes a bit of hand work). What I would like
> to do, is continue to init the "test" database. To make that easy, I would
> like to be able to "export" individual tables, so I can use the scripts to
> reload them. I prefer not to have to convert these to my load script
> format.
>
> Is there a way to "export" a single table, that can be easily re
> "imported"?
>
>
> --
> "They that would give up essential liberty for temporary safety deserve
> neither liberty nor safety."
> -- Benjamin Franklin
>
It may be a strange suggestion but did you consider containers like Docker?
It's been a great help on a 100GB+ test database. Successful changes were
committed, failed changes were rolled back creating a new instance based on
the same image (with data preloaded). It takes seconds to do a rollback.
Olivier
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jason Ralph | 2019-09-13 15:10:50 | PANIC: could not write to file "pg_wal/xlogtemp.11399": No space left on device |
Previous Message | Hans Schou | 2019-09-13 14:39:06 | Re: backing up the data from a single table? |