When adding an index to a (quite large, ~2 million rows) table
PostgreSQL continues to do sequential lookups until VACUUM ANALYZE is
run. Naturally performance is poor.
The CREATE INDEX statement takes considerable time.
Seen with 7.1.3 on Intel Linux (RedHat 7.0 7.1 and Solaris 2.6.
In the
be functionally similar to
_bt_check_unique but obviously higher level. Is there any existing
code with the functionality I desire? Can anyone point me in the right
way...
Thanks,
Lee Kindness.
Lee Kindness writes:
I'm in the process of porting a large application from Ingres to
PostgreSQL. We make
Peter Eisentraut writes:
However, it seems to me that COPY ignoring duplicates can easily be
done by preprocessing the input file.
Or by post-processing, like (error checking cut):
void import_shots(char *impfile, int lineshoot_id)
{
char tab_name[128];
char tab_temp[128];
|TERMINATE (or similar)
need to be added to the COPY command (I hope not)?
Thanks,
--
Lee Kindness, Senior Software Engineer
Concept Systems Limited.
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Justin Clift writes:
Lee Kindness wrote:
WITH ON_DUPLICATE = CONTINUE|TERMINATE (or similar)
I would suggest :
WITH ON_DUPLICATE = IGNORE|TERMINATE
purely for easier understanding, given there is no present standard nor
other databases' syntax to conform to.
Personally I don't see
Tom Lane writes:
Lee Kindness [EMAIL PROTECTED] writes:
Would this seem a reasonable thing to do? Does anyone rely on COPY
FROM causing an ERROR on duplicate input?
Yes. This change will not be acceptable unless it's made an optional
(and not default, IMHO, though perhaps that's
Okay,
If I'm going to modify 'COPY INTO' to include 'ignore duplicates'
functionality it looks like I'll have to add to the COPY syntax. The
most obvious way is to add:
WITH IGNORE DUPLICATES
to the syntax. I'm going to need my hand held a bit for this! The
grammar for COPY will need updating
Lee Kindness writes:
If I'm going to modify 'COPY INTO' to include 'ignore duplicates'
functionality it looks like I'll have to add to the COPY syntax. The
most obvious way is to add:
WITH IGNORE DUPLICATES
Or does it make more sense to add a 'COPY_IGNORE_DUPLICATES' SET
parameter
101 - 108 of 108 matches
Mail list logo
