| From: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tomas Vondra <tomas(at)vondra(dot)me>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Why mention to Oracle ? |
| Date: | 2024-09-20 17:31:47 |
| Message-ID: | CAB-JLwau7BVCqDRvp56LD=KWiuQWPHatHOjXPLLszaUaRhdXJQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Em sex., 20 de set. de 2024 às 12:53, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> escreveu:
> As far as the mentions in "Data Type Formatting Functions" go, those
> are there because those functions are not in the SQL standard; we
> stole the API definitions for them from Oracle, lock stock and barrel.
> (Except for the discrepancies that are called out by referencing what
> Oracle does differently.) A number of the other references probably
> have similar origins.
>
All the time we see somebody adding a new function to Postgres core that
exists in Python or GO or MySQL, but none of them are mentioned on DOCS.
I did never use Oracle but I'm almost sure on Oracle DOCS there are no
mentions of Postgres, right ? Why do we need to mention it ?
Regards
Marcos
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marcos Pegoraro | 2024-09-20 17:42:17 | Re: Why mention to Oracle ? |
| Previous Message | Masahiko Sawada | 2024-09-20 17:22:50 | Re: Using per-transaction memory contexts for storing decoded tuples |