| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | "Rossi, Maria" <maria(dot)rossi(at)jackson(dot)com>, "'pgsql-sql(at)lists(dot)postgresql(dot)org'" <pgsql-sql(at)lists(dot)postgresql(dot)org>, "'pgsql-novice(at)lists(dot)postgresql(dot)org'" <pgsql-novice(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_dumpall and restore |
| Date: | 2018-10-09 18:32:02 |
| Message-ID: | 19950.1539109922@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice pgsql-sql |
Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> Rossi, Maria wrote:
>> Has anyone encountered having dups rows loaded? Any idea what caused this and how to prevent?
> I don't believe that pg_dumpall miraculously duplicated the row.
What seems much more likely is that the dump script was loaded twice.
The script expects to be fed into an empty database ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rossi, Maria | 2018-10-09 20:05:59 | RE: pg_dumpall and restore |
| Previous Message | Laurenz Albe | 2018-10-09 18:28:25 | Re: pg_dumpall and restore |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher McDonald | 2018-10-09 19:01:10 | remove from list? |
| Previous Message | Laurenz Albe | 2018-10-09 18:28:25 | Re: pg_dumpall and restore |