Igor Diakonov
|
0ca035d7ef
|
Added jobs count
|
5 years ago |
Igor Diakonov
|
3348023d8f
|
Added multithreading
|
5 years ago |
Igor Diakonov
|
b7118f48cb
|
Fixed pg_restore flag
|
5 years ago |
Igor Diakonov
|
e04083c6eb
|
Changed psql to pg_restore
|
5 years ago |
Igor Diakonov
|
2f86476c60
|
Changed psql to pg_restore
|
5 years ago |
Igor Diakonov
|
4b2d13bc6d
|
Return back to first variant
|
5 years ago |
Igor Diakonov
|
2b3a4a0da3
|
Added recreating existing tables
|
5 years ago |
Igor Diakonov
|
b43a498772
|
Added recreating existing tables
|
5 years ago |
Igor Diakonov
|
e182fb06a6
|
Added s3 endpoint to postgres-restore-s3
|
5 years ago |
Konstantin Shilovskiy
|
ce7af27ab9
|
Use latest alpine versions
|
7 years ago |
Jérôme Parmentier
|
c2c45be6bb
|
Replace deprecated MAINTAINER by LABEL
|
7 years ago |
Santiago Palladino
|
51d17b5836
|
Upgrade alpine version from 3.2 to 3.4 for pgbackup images
Version 3.2 has an incompatibility with docker cloud: it cannot
resolve services, due to a resolv.conf issue. Latest version seems
to work fine.
|
8 years ago |
Kieran Brownlees
|
f80eac5ad3
|
Update readme for postgres restore
|
9 years ago |
Kieran Brownlees
|
d73875f1ea
|
Use alpine:3.2 & postgres 9.4
|
9 years ago |
Kieran Brownlees
|
865f8b2798
|
postgres-restore-s3
Pretty basic and is dangerous, but seems to work.
There is an option to drop the current public schema
|
9 years ago |