| From: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
|---|---|
| To: | Tim Uckun <timuckun(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Upsert Functionality using CTEs |
| Date: | 2013-02-11 06:05:24 |
| Message-ID: | CAL_0b1vqVLW0p=Qf=iiQHf79F0FvZXyiBOhNd6Z=uCgm-WyBOg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Feb 10, 2013 at 5:23 PM, Tim Uckun <timuckun(at)gmail(dot)com> wrote:
> This works pretty good except for when the top 100 records have
> duplicated email address (two sales for the same email address).
How is it assumed to work when the migrating email already exists in people?
>
> I am wondering what the best strategy is for dealing with this
> scenario. Doing the records one at a time would work but obviously it
> would be much slower. There are no other columns I can rely on to
> make the record more unique either.
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
--
Sergey Konoplev
Database and Software Architect
http://www.linkedin.com/in/grayhemp
Phones:
USA +1 415 867 9984
Russia, Moscow +7 901 903 0499
Russia, Krasnodar +7 988 888 1979
Skype: gray-hemp
Jabber: gray(dot)ru(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2013-02-11 06:23:51 | Re: REINDEX deadlock - Postgresql -9.1 |
| Previous Message | Anoop K | 2013-02-11 05:55:50 | Re: REINDEX deadlock - Postgresql -9.1 |