Patrick B wrote: > I am running a background task on my DB, which will copy data from tableA to tableB. For > that, I'm writing a PL/PGSQL function which basically needs to do the following: > > > 1. Select the data from tableA > 2. The limit will be put when calling the function > 3. insert the selected data on Step 1 onto new table > > Question: > > * When I stop it and start it again, how can the query "know" that it has already > processed some rows so it won't do it twice on the same rows? If it stopped on row number > 100, I need it to continue on row number 101, for example. > > * How can I ask the function to return the number of processed rows? > > > I can add a column on TableB if needed, but not on tableA. > > This is what I've done so far: > CREATE or REPLACE FUNCTION data_copy(rows integer) > RETURNS SETOF bigint AS $$ CREATE or REPLACE FUNCTION data_copy(p_limit integer, p_offset integer) RETURNS integer; > declare > row record; > offset_num integer; num_rows integer := 0; > BEGIN > FOR row IN EXECUTE ' > SELECT > id, > path, > name, > name_last, > created_at > FROM > tablea > WHERE > ready = true > ORDER BY 1 LIMIT ' || rows || ' OFFSET ' || rows || '' '... LIMIT ' || p_limit || ' OFFSET ' || p_offset > LOOP num_rows := num_rows + 1; > INSERT INTO tableB (id,path,name,name_last,created_at) > VALUES (row.id,row.path,row.name,row.name_last,row.created_at); > > END LOOP; RETURN num_rows; > END > $$ language 'plpgsql'; There are two problems with this approach: 1. It will do the wrong thing if rows are added or deleted in "tablea" while you process it. 2. Queries with hight OFFSET values have bad performance. The solution is to avoid OFFSET and to use "keyset pagination": http://use-the-index-luke.com/no-offset Yours, Laurenz Albe -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
