public inbox for [email protected]  
help / color / mirror / Atom feed
From: [email protected] <[email protected]>
To: Robert Burgholzer <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: stop
Date: Fri, 29 Apr 2022 17:51:54 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CACT-NGJ5VP4R+zx_aAerzCUBD2-k0Wf9UwgTOOp=A84EUyaAiA@mail.gmail.com>
References: <CACT-NGJ5VP4R+zx_aAerzCUBD2-k0Wf9UwgTOOp=A84EUyaAiA@mail.gmail.com>

Dag, should have enabled those darn checksums!

Sent from my iPhone

> On Apr 29, 2022, at 5:22 PM, Robert Burgholzer <[email protected]> wrote:
> 
> 
> I believe if you reply "don't, don't, don't let's start" that all Listserv's will process your request accordingly.
> 
>> On Fri, Apr 29, 2022 at 4:43 PM Tim <[email protected]> wrote:
>> 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 <[email protected]> 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 <[email protected]> wrote:
>>>>>> On Thu, Apr 28, 2022 at 12:53 PM Tony Farrell <[email protected]> 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
>>> [email protected]
> -- 
> --
> Robert W. Burgholzer
>  'Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that's creativity.'  - Charles Mingus


view thread (7+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: stop
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox