| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | <heikki(dot)linnakangas(at)enterprisedb(dot)com>,<kaigai(at)kaigai(dot)gr(dot)jp> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org>,<tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Inserting heap tuples in bulk in COPY |
| Date: | 2011-09-25 16:02:46 |
| Message-ID: | 4E7F0A5602000025000416B3@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Kohei KaiGai wrote:
> I'm not clear the reason why the argument of
> CheckForSerializableConflictIn() was changed from the one in
> heap_insert().
The code was probably just based on heap_insert() before this recent
commit:
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=9d306c66e63eb7f45eab9475b3f96c3134bacac6
> Is it feasible that newly inserted tuples conflict with existing
> tuple locks when we expand insert to support multiple tuples at
> once?
No.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-09-25 16:04:29 | Re: Alter column...using failure under 9.0.4 |
| Previous Message | Robert Haas | 2011-09-25 16:01:36 | Re: Inserting heap tuples in bulk in COPY |