pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: M Sarwar <sarwarmd02@outlook.com>
To: Ron Johnson <ronljohnsonjr@gmail.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Enhancement Request
Date: Fri, 2 Feb 2024 01:50:41 +0000
Message-ID: <DM4PR19MB5978ACC9AC9216F5A2AFAC3AD3422@DM4PR19MB5978.namprd19.prod.outlook.com> (raw)
In-Reply-To: <CANzqJaCDHrN+pu=mbMhg1_so_+KWUmE1ZvRUhyJ_Et2WB+WPcg@mail.gmail.com>
References: <SJ0PR11MB56294F4A249D780BC3A18330DE7C2@SJ0PR11MB5629.namprd11.prod.outlook.com>
	<CH0PR02MB8106DCF6427AD9045CB5DD77E57C2@CH0PR02MB8106.namprd02.prod.outlook.com>
	<DM4PR19MB5978E8D391D422D086632D89D37C2@DM4PR19MB5978.namprd19.prod.outlook.com>
	<CH0PR02MB81063B5272D9663465788281E57C2@CH0PR02MB8106.namprd02.prod.outlook.com>
	<DM4PR19MB597863302D9DE35498BC4CA7D37C2@DM4PR19MB5978.namprd19.prod.outlook.com>
	<CANzqJaCDHrN+pu=mbMhg1_so_+KWUmE1ZvRUhyJ_Et2WB+WPcg@mail.gmail.com>

Hi Ron,

I appreciate asking this question.   For me, it is a complex question and it is an evolving idea.
When we use LIMIT clause in the SQL, SQL may be used in with / without ORDER of ASC / DESC,  UUID, Pseudo columns, ROWNUM, etc clauses.  When we use ORDER by,  LIMIT may be ok to DELETE but in the ROWNUM, other pseudo columns presence impact is hard to foresee.
In the DELETE statement, there may be WHERE conditions.  It is likely to complicate. If it is a simple DELETE statement with just LIMIT clause, it is hard to foresee and likely to complicate. Without a ORDER BY clause in the SQL, LIMIT will complicate the scenario.

 You may collect the opinion from few others and make a decision on this.

Thanks,
Sarwar


________________________________
From: Ron Johnson <ronljohnsonjr@gmail.com>
Sent: Wednesday, January 31, 2024 8:31 PM
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Enhancement Request

On Wed, Jan 31, 2024 at 3:55 PM M Sarwar <sarwarmd02@outlook.com<mailto:sarwarmd02@outlook.com>> wrote:
If they allow DELETE FROM-LIMT to work, it is going to harm  the general interest of the database.
In my opinion, that should not be implemented.

Why would it harm the general interest of the database?

What even does "the general interest of the database" mean?


view thread (45+ messages)  latest in thread

Message-ID: <DM4PR19MB5978ACC9AC9216F5A2AFAC3AD3422@DM4PR19MB5978.namprd19.prod.outlook.com>
Permalink:  ../DM4PR19MB5978ACC9AC9216F5A2AFAC3AD3422@DM4PR19MB5978.namprd19.prod.outlook.com/
Also on:    postgresql.org/message-id/DM4PR19MB5978ACC9AC9216F5A2AFAC3AD3422@DM4PR19MB5978.namprd19.prod.outlook.com

 · 

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-admin@postgresql.org
  Cc: sarwarmd02@outlook.com, ronljohnsonjr@gmail.com
  Subject: Re: Enhancement Request
  In-Reply-To: <DM4PR19MB5978ACC9AC9216F5A2AFAC3AD3422@DM4PR19MB5978.namprd19.prod.outlook.com>

* 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