pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: dzja112@gmail.com
Subject: BUG #18531: err when using 'current of' with incremental COMMIT
Date: Tue, 09 Jul 2024 11:00:29 +0000
Message-ID: <18531-c6dddd33b8555fd2@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      18531
Logged by:          Dzmitry Jachnik
Email address:      dzja112@gmail.com
PostgreSQL version: 14.2
Operating system:   x86_64 GNU/Linux
Description:        

I tried using 'current of' syntax (like doc. 43.7.3.3.)
and had have ERROR: cursor "bulk_collection_cur" is held from a previous
transaction

If using regular ` WHERE id = l_rec.id; ` I hadn't any error

EXAMPLE:
```

CREATE OR REPLACE PROCEDURE crm_import.etlp_deals(IN i_id bigint DEFAULT
NULL::bigint, IN i_limit integer DEFAULT null)
 LANGUAGE plpgsql
AS $procedure$ 
DECLARE

  result jsonb;
  COUNTER int := 0;
 
  bulk_collection_cur CURSOR FOR
  		SELECT *
          FROM crm_import.deals dew
         WHERE COALESCE(dew.etl_stage,'NOT_LOADED') not IN ('LOADED',
'IGNORE')
--           AND dew.id = any(l_id)
           AND (dew.id = i_id OR i_id IS null)
         ORDER BY dew.load_date, dew.dt
           FOR UPDATE ;
begin

	<<COLLECTION>>
	BEGIN 
		FOR l_rec IN bulk_collection_cur
		LOOP 
	    	COUNTER := COUNTER + 1;
			RESULT := crm_import.etl_deals(row_to_json(l_rec.*)::jsonb);
		     
	    	UPDATE crm_import.deals dsp
	           SET etl_protocol = RESULT
	        -------------------
	        --v.1 SQL Error [24000]: ERROR: cursor "bulk_collection_cur" is
held from a previous transaction
	    	WHERE CURRENT OF bulk_collection_cur;
	        --v.2 WITHOUT ERROR
	        --WHERE id = l_rec.id; 					
			-------------------
	    	RAISE NOTICE 'counter= %', counter;
			IF mod(counter, i_limit) = 0 THEN
				RAISE NOTICE 'COMMIT';
		    	COMMIT;
		    END IF;
		END LOOP;
	END COLLECTION;

end $procedure$
;
```
That combine 'current of' and 'commit' at one loop is bad idea?



view thread (2+ messages)  latest in thread

Message-ID: <18531-c6dddd33b8555fd2@postgresql.org>
Permalink:  ../18531-c6dddd33b8555fd2@postgresql.org/
Also on:    postgresql.org/message-id/18531-c6dddd33b8555fd2@postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, dzja112@gmail.com
  Subject: Re: BUG #18531: err when using 'current of' with incremental COMMIT
  In-Reply-To: <18531-c6dddd33b8555fd2@postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox