"David G. Johnston" writes:
> On Mon, Aug 17, 2020 at 10:11 AM Tom Lane wrote:
>> Yeah, me either. So here's a proposed patch, fixing a couple other
>> things:
> LGTM
Pushed, thanks for review.
regards, tom lane
On Mon, Aug 17, 2020 at 10:11 AM Tom Lane wrote:
> "David G. Johnston" writes:
> > On Mon, Aug 17, 2020 at 8:31 AM Tom Lane wrote:
> >> So this is just a verbatim statement of the algorithm, which is what
> >> I was hoping to avoid :-(. But maybe there's no simpler way.
>
> > I got nothin'.
>
On Fri, Aug 14, 2020 at 01:32:35PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/12/runtime-config-wal.html
> Description:
>
> Hello,
>
> First of all I would like to say that PostgreSQL has the
"David G. Johnston" writes:
> On Mon, Aug 17, 2020 at 8:31 AM Tom Lane wrote:
>> So this is just a verbatim statement of the algorithm, which is what
>> I was hoping to avoid :-(. But maybe there's no simpler way.
> I got nothin'.
Yeah, me either. So here's a proposed patch, fixing a couple
I know we talk about durability a lot, but it seems we mention "stable
storage" much more often than "durable storage" in our docs:
$ grep 'stable storage' *.sgml
config.sgml:necessarily reached stable storage on the standby.
monitoring.sgml: stable storage.
On Mon, Aug 17, 2020 at 8:31 AM Tom Lane wrote:
> "David G. Johnston" writes:
> > More concisely:
>
> > Make the first input type a candidate type. Each subsequent input type
> is
> > compared to the current candidate, with a new candidate being chosen only
> > when there exists a non-mutal
"David G. Johnston" writes:
> More concisely:
> Make the first input type a candidate type. Each subsequent input type is
> compared to the current candidate, with a new candidate being chosen only
> when there exists a non-mutal implicit cast to the new type. If at any
> point a preferred
