MIME-Version: 1.0
References: <CABvPt_xtYyvFfyupGn=TXNGnEAFd0m_ARPFpDUWBcn603aM84w@mail.gmail.com>
 <1554256.1729521467@sss.pgh.pa.us> <CABvPt_zjW7oVeYg9SMtYre0cG_Jm_mxPiErZMvf2Eco-hOcDxA@mail.gmail.com>
 <dddad51b-4f53-4baa-be88-822caab9f900@aklaver.com>
In-Reply-To: <dddad51b-4f53-4baa-be88-822caab9f900@aklaver.com>
Reply-To: zarkonesmall@gmail.com
From: Anatolii Smolianinov <zarkonesmall@gmail.com>
Date: Mon, 21 Oct 2024 18:00:15 +0200
Message-ID: <CABvPt_z1T=LPoRxC78tixvur9d41az4Ben=FYMp0dsWVf4zWLA@mail.gmail.com>
Subject: Re: Timezone: resolve $TZDIR in runtime
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000004503980624fec018"
Archived-At: <https://www.postgresql.org/message-id/CABvPt_z1T%3DLPoRxC78tixvur9d41az4Ben%3DFYMp0dsWVf4zWLA%40mail.gmail.com>
Precedence: bulk

--0000000000004503980624fec018
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=AFPM Adrian Klaver <adrian.klaver@aklave=
r.com>
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@aklaver.com
>
>

--0000000000004503980624fec018
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Adrian! <br></div><div><br></div><div>Totally agre=
e.=C2=A0</div><div><br></div><div>I think embedded postgresql appeared main=
ly because of compatibility reasons. If you are using postgres on server, w=
ith some of the custom features which you can&#39;t find in other databases=
, and want to enable &quot;local mod&quot; for your users, (and also for te=
sts maybe), but you don&#39;t want to roll out a compatibility layer with e=
.g. sqlite.</div><div><br></div><div>As I&#39;ve mentioned, it&#39;s not ab=
out embedded really, it is more about support of standard $TZDIR mechanics =
in general. Embedded postgresql was mentioned just for the context of my us=
e case.<br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" clas=
s=3D"gmail_attr">On Mon, Oct 21, 2024 at 5:53=E2=80=AFPM Adrian Klaver &lt;=
<a href=3D"mailto:adrian.klaver@aklaver.com">adrian.klaver@aklaver.com</a>&=
gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 10=
/21/24 08:03, Anatolii Smolianinov wrote:<br>
&gt; Hi Tom, thanks for your reply!<br>
&gt; <br>
&gt; I understand your point, and also, the idea of embedding postgresql --=
 <br>
&gt; it might be just not what postgresql is built for. I was just thinking=
 <br>
&gt; that respecting the standard TZDIR approach would add more flexibility=
.<br>
<br>
<a href=3D"https://wiki.postgresql.org/wiki/Not_Worth_Doing#Features_We_Do_=
Not_Want" rel=3D"noreferrer" target=3D"_blank">https://wiki.postgresql.org/=
wiki/Not_Worth_Doing#Features_We_Do_Not_Want</a><br>
<br>
&quot;Embedded server<br>
=C2=A0 =C2=A0 =C2=A0While PostgreSQL clients runs fine in limited-resource =
<br>
environments, the server requires multiple processes and a stable pool <br>
of resources to run reliably and efficiently. Stripping down the <br>
PostgreSQL server to run in the same process address space as the client <b=
r>
application would add too much complexity and failure cases. Besides, <br>
there are several very mature embedded SQL databases already available. &qu=
ot;<br>
<br>
<br>
<br>
<br>
-- <br>
Adrian Klaver<br>
<a href=3D"mailto:adrian.klaver@aklaver.com" target=3D"_blank">adrian.klave=
r@aklaver.com</a><br>
<br>
</blockquote></div>

--0000000000004503980624fec018--