Re: Why mention to Oracle ? - Mailing list pgsql-hackers

From Jonah H. Harris
Subject Re: Why mention to Oracle ?
Date
Msg-id CADUqk8VbTEohcE0gkgrsBZ4WUdzKmLk==J_tR8NN37dxvBN5og@mail.gmail.com
Whole thread Raw
In response to Re: Why mention to Oracle ?  (Marcos Pegoraro <marcos@f10.com.br>)
Responses Re: Why mention to Oracle ?
List pgsql-hackers
On Fri, Sep 20, 2024 at 4:27 PM Marcos Pegoraro <marcos@f10.com.br> wrote:
Em sex., 20 de set. de 2024 às 15:11, Tomas Vondra <tomas@vondra.me> escreveu:
IMHO it's quite reasonable to say "we do X, but this other product
(which is what we try to mimic) does Y".

Ok, for Data Type Formatting Functions is fine, if they were really copied from, but the others ...
Bug Reporting Guidelines, LOCK, SELECT, ROLLBACK TO SAVEPOINT and CURSORS

Seems to me this has already been answered well multiple times by multiple people; I’m not sure why this is such an issue, or one that warrants continued discussion.

By your own admission, you wouldn’t see the value, where others who came from Oracle would. Additionally, your assumption is incorrect: many Oracle databases are migrated to Postgres, more-so today than when much of that was written.

You’re arguing against it being in the docs and talking about how much better it would be in other more focused content, which does have some merit. But, at the same time, you’re neither qualified nor volunteering to write it. As such, getting rid of it here serves what purpose other than omitting useful information to those it would benefit directly in the documentation?


pgsql-hackers by date:

Previous
From: Marcos Pegoraro
Date:
Subject: Re: Why mention to Oracle ?
Next
From: Masahiko Sawada
Date:
Subject: Re: Pgoutput not capturing the generated columns