| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "Martijn Tonies (Upscene Productions)" <m(dot)tonies(at)upscene(dot)com>, Dominique Devienne <ddevienne(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Stored procedure code no longer stored in v14 and v15, changed behaviour |
| Date: | 2022-12-02 12:37:11 |
| Message-ID: | a60a3f60d791cc0291deafc775ffdbb2a6161c56.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 2022-12-02 at 08:49 +0100, Martijn Tonies (Upscene Productions) wrote:
> So do InterBase, Firebird, SQL Server, MySQL (except for Views, strangely
> enough),
> MariaDB, NexusDB, SQL Anywhere, and, frankly, all others I know of.
>
> And this is used all the time by database developers.
>
> And at least InterBase and Firebird -also- stored a 'parsed version' (in
> binary).
Great; then go ahead and use those databases, if it is important for you.
In the same vein, I don't think any of those databases have trigram or
bloom indexes. Perhaps we should improve the acceptance of PostgreSQL
by removing those features?
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pasi Oja-Nisula | 2022-12-02 13:00:09 | Re: Stored procedure code no longer stored in v14 and v15, changed behaviour |
| Previous Message | jacktby@gmail.com | 2022-12-02 12:00:31 | modify planner codes, get failed |