Re: Improve explicit cursor handling in pg_stat_statements - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: Improve explicit cursor handling in pg_stat_statements
Date
Msg-id CAA5RZ0tktrA3R-xb5+aeGGjWP9ZSqHspzicO-foEthDdP+5GJA@mail.gmail.com
Whole thread Raw
In response to Improve explicit cursor handling in pg_stat_statements  (Sami Imseih <samimseih@gmail.com>)
List pgsql-hackers
> Should we offer something more consistent with DeallocateStmt, where
> we have a boolean flag that would be set when ALL is specified,
> included in the jumbling?  This would mean two separate entries: one
> for the constants and one for ALL.

Hmm, we could do that to differentiate the keyword ALL. I had a thought
earlier about differentiating the other keywords as well: FIRST, LAST,
BACKWARD, FORWARD, and ABSOLUTE. Initially, I thought it might
be a bit too much, but I do see the merit in this approach, as these are
syntactically different from their numeric counterparts.

We can accomplish this with just an extra field in FetchStmt, where each
of these keywords gets a distinct value.

What do you think?

--
Sami



pgsql-hackers by date:

Previous
From: Robert Treat
Date:
Subject: Re: Suggestions for improving \conninfo output in v18
Next
From: Amit Kapila
Date:
Subject: Re: Logical Replication of sequences