| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | zarkonesmall(at)gmail(dot)com, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Timezone: resolve $TZDIR in runtime |
| Date: | 2024-10-21 15:53:07 |
| Message-ID: | dddad51b-4f53-4baa-be88-822caab9f900@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anatolii Smolianinov | 2024-10-21 16:00:15 | Re: Timezone: resolve $TZDIR in runtime |
| Previous Message | Anatolii Smolianinov | 2024-10-21 15:03:14 | Re: Timezone: resolve $TZDIR in runtime |