Hi Adrian!
Totally agree.
I think embedded postgresql appeared mainly because of compatibility reasons. If you are using postgres on server, with some of the custom features which you can't find in other databases, and want to enable "local mod" for your users, (and also for tests maybe), but you don't want to roll out a compatibility layer with e.g. sqlite.
As I've mentioned, it's not about embedded really, it is more about support of standard $TZDIR mechanics in general. Embedded postgresql was mentioned just for the context of my use case.
On Mon, Oct 21, 2024 at 5:53 PM Adrian Klaver <adrian.klaver@xxxxxxxxxxx> wrote:
On 10/21/24 08:03, Anatolii Smolianinov wrote:
> Hi Tom, thanks for your reply!
>
> I understand your point, and also, the idea of embedding postgresql --
> it might be just not what postgresql is built for. I was just thinking
> that respecting the standard TZDIR approach would add more flexibility.
https://wiki.postgresql.org/wiki/Not_Worth_Doing#Features_We_Do_Not_Want
"Embedded server
While PostgreSQL clients runs fine in limited-resource
environments, the server requires multiple processes and a stable pool
of resources to run reliably and efficiently. Stripping down the
PostgreSQL server to run in the same process address space as the client
application would add too much complexity and failure cases. Besides,
there are several very mature embedded SQL databases already available. "
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
