From: | Tim <timfosho(at)gmail(dot)com> |
---|---|
To: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Tony Farrell <pithhelmet(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: stop |
Date: | 2022-04-29 20:43:18 |
Message-ID: | CAKhLO5jtZZiZ0axQ5Pw7dyiiABfQBOuNdL1qzOz=mQOL8g3Lrw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
What does it mean to "stop" anyway? Aren't we all just transactions in the
snapshot of the universe without a rollback? Our xmin approaches with each
passing day. If only I could PITR to my youth, maybe then I could recover
that which was long corrupted. If only I had checksums enabled.
On Thu, Apr 28, 2022 at 4:56 PM Wells Oliver <wells(dot)oliver(at)gmail(dot)com> wrote:
> In my experience, it won't stop, it never stops, asking it to stop, indeed
> throwing yourself on the public's mercy pleading for it to stop will only
> insure a renewed intensity. Godspeed, Tony.
>
>
>
> On Thu, Apr 28, 2022 at 1:18 PM David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>> On Thu, Apr 28, 2022 at 12:53 PM Tony Farrell <pithhelmet(at)gmail(dot)com>
>> wrote:
>>
>>> stop
>>>
>>>
>> Someone may help you (but there are no promises) but if you wish to take
>> control of your own destiny read the following for self-service.
>>
>> https://lists.postgresql.org/unsubscribe/
>> David J.
>>
>>
>
> --
> Wells Oliver
> wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Burgholzer | 2022-04-29 21:21:57 | Re: stop |
Previous Message | MARIANE K | 2022-04-29 12:15:54 | Question abouth ssl_ciphers Amazon RDS postgres |