Search Postgresql Archives

Re: Suggestions for blocking user inserts during admin bulk loading.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Woody Woodring" <george.woodring@xxxxxxxxxx> writes:
> The following is the procedure I use for updating the entire table, mac is
> the primary key:

> truncate master;
> create temp_table;
> COPY "temp_table" (mac, . . .) FROM stdin WITH DELIMITER AS '|';
> UPDATE master SET mac=temp_table.mac . . . FROM temp_table WHERE
> master.mac=temp_table.mac;
> LOCK master IN EXCLUSIVE MODE;  -- Added this step to keep user out to avoid
> conflicts, not really working
> INSERT INTO master (mac, . . .) SELECT mac, . . . FROM temp_table WHERE mac
> NOT IN (SELECT mac from master) ORDER BY mac;

I suspect the reason it's not working is that a LOCK only lasts the
duration of the current transaction, which is only that statement itself
if you have no BEGIN block around it.  What you want is something like

truncate ...
...
BEGIN;
LOCK master IN EXCLUSIVE MODE;
INSERT INTO master (mac, . . .) SELECT mac, . . . FROM temp_table WHERE mac
NOT IN (SELECT mac from master) ORDER BY mac;
COMMIT;

Whether this is the best solution is not clear, but at least it would
work like you expected.

			regards, tom lane

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux