Thank you for the insights
On Wed, Nov 22, 2023 at 5:09 PM Laurenz Albe
wrote:
>
> One of the problems is what should be included.
> Indexes? Policies? Constraints?
>
A high limit could be all objects except data.
All the objects which would be deleted by a 'DROP TABLE'.
Maybe including 'CASCADE'?
No unsurmountable
> On Mar 31, 2024, at 09:59, Peter J. Holzer wrote:
> Is this an acceptable performance penalty per API call? If not, is it
> really necessary to check this on every call? Maybe it can be done just
> once per session or once per hour.
It's probably not required to check it every API call.
On 2024-03-30 09:23:15 -0400, Ron Johnson wrote:
> On Sat, Mar 30, 2024 at 9:15 AM 黄宁 wrote:
>
> I want to develop a postgresql paid extension, then there is a local
> license file, how do I check if the license file is expired, check it once
> at each api execution, will that affect
On Sat, 30 Mar 2024, 10:04 Alexander Farber,
wrote:
> Thank you, Justin -
>
> On Sat, Mar 30, 2024 at 4:33 AM Justin Clift
> wrote:
>
>> On 2024-03-30 05:53, Alexander Farber wrote:
>> > I use the following postgresql.conf in my Dockerfile
>> > ( the full version at
On 2024-03-31 04:07, Alexander Farber wrote:
Turning fsync = off has resulted in no noticable build time reduction
for
my Dockerfile with OSM Europe data, but still thank you for the
suggestion!
No worries. :)
With this import you're doing, is it something that will be repeated a
lot
with
