Date: Fri, 26 Jun 2020 19:59:54 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Martin Handsteiner <martin.handsteiner@sibvisions.com>
Cc: "pgsql-sql@lists.postgresql.org" <pgsql-sql@lists.postgresql.org>
Subject: Re: Optimizer Hint, to ignore limit and offset in optimizer plan
Message-ID: <20200626235954.GA3324@momjian.us>
References: 
 <VI1PR1001MB1423F5361320BB854708FD2FE8930@VI1PR1001MB1423.EURPRD10.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <VI1PR1001MB1423F5361320BB854708FD2FE8930@VI1PR1001MB1423.EURPRD10.PROD.OUTLOOK.COM>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Fri, Jun 26, 2020 at 08:49:19AM +0000, Martin Handsteiner wrote:
> Hello,
> 
>  
> 
> I’m aware, that taking limit and offset into account of optimizer plan is not a
> bug.
> 
> Nevertheless it is very often an unwanted feature.
> 
> As the postgres db has the issue with not supporting cursors over commit/
> rollback, it is necessary to use the limit and offset mechanism.

Uh, have you considered WITH HOLD cursors:

	WITH HOLD specifies that the cursor can continue to be used after the
	transaction that created it successfully commits.  WITHOUT HOLD
	specifies that the cursor cannot be used outside of the transaction that
	created it. If neither WITHOUT HOLD nor WITH HOLD is specified, WITHOUT
	HOLD is the default.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee