| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Don Baccus <dhogaza(at)pacifier(dot)com> |
| Cc: | Karel Zak - Zakkr <zakkr(at)zf(dot)jcu(dot)cz>, "Ross J(dot) Reedstrom" <reedstrm(at)wallace(dot)ece(dot)rice(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, t-ishii(at)sra(dot)co(dot)jp, pgsql-hackers <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] compression in LO and other fields |
| Date: | 1999-11-12 22:11:12 |
| Message-ID: | 382C9080.103696C9@tm.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Don Baccus wrote:
>
> At 05:15 PM 11/12/99 +0100, Karel Zak - Zakkr wrote:
>
> >> pg_dump database | gzip >db.out.gz
>
> > Thank... :-))
>
> > But mysqldump --compress is very nice.
>
> Why add functionality for something that can be done so
> easily by piping the output of pg_dump?
>
> This is exactly the kind of coupling of tools that pipes
> were invented for.
Exactly !
Another version of the same is used when dumping databases
bigger than 2GB (or whatever the file system size limit is)
just do:
pg_dump database | gzip | split -b 1000000000 db.out.gz.
and restore it using
cat db.out.gz* | gunzip > psql
you could also do other fancy things with your dumps - send
them directly to tape storage in Japan or whatever ;)
If you need that functionality often enough then write a shell
script.
---------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frans Van Elsacker | 1999-11-12 23:31:30 | Re: [HACKERS] union problem version 6.5.3 |
| Previous Message | Hannu Krosing | 1999-11-12 22:02:54 | Re: [HACKERS] compression in LO and other fields |