From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | annadurai02145(at)outlook(dot)com |
Subject: | BUG #18605: cursor select not working |
Date: | 2024-09-09 05:04:48 |
Message-ID: | 18605-d50c6475ffe40bcf@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 18605
Logged by: ANNADURAI s
Email address: annadurai02145(at)outlook(dot)com
PostgreSQL version: 15.5
Operating system: pg admin tool
Description:
BEGIN;
DECLARE
my_cursor CURSOR FOR SELECT * FROM example;
FETCH all FROM my_cursor;-------------------i have execute the script get
record row
BEGIN;
DECLARE
my_cursor CURSOR FOR SELECT * FROM example;
FETCH all FROM my_cursor;
end;-----------this script execute no row found we need clarification
------------------------------------------------------------------------------------------------------
i have create select procedure return cursor output execute this one
unammend port1 error showing we need clarification this one also
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2024-09-09 07:21:19 | Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows |
Previous Message | Basha | 2024-09-07 18:57:25 | Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications |