>
> I'd say that the storag order is the order in which PostgreSQL stores
> multiranges internally:
Right, I believe that you are right but then this information is not useful
for the developer.
If storage order is always ascending by range order then let's make it
clear, if order cannot be count
"David G. Johnston" writes:
> On Tue, Oct 3, 2023 at 2:48 PM PG Doc comments form
> wrote:
>> But mentioned section 26.3.3 does not describe `spread` mode:
> It does, though it is phrased in terms of "fast => false" meaning "spread"
> whereas "fast => true" means "immediate".
> But since the CLI
I was trying to figure how to set the log directory on my Windows client
using a parameter in the connection string. Short answer is that you can't.
But you can using the DSN settings.
I was under the impression that going DSN-less and using the parameters on
the connection string, we were free f
On Tue, Oct 3, 2023 at 2:48 PM PG Doc comments form
wrote:
>
> On [this
> page](https://www.postgresql.org/docs/current/app-pgbasebackup.html)
> `spread` is mentioned:
>
> -c {fast|spread}
> --checkpoint={fast|spread}
>
> Sets checkpoint mode to fast (immediate) or spread (the default) (see
>
PG Doc comments form writes:
> According to your example (copied from your docs):
> -- includes 3, does not include 7, and does include all points in between
> SELECT '[3,7)'::int4range;
> But this is not true, it shows 3 and 7
What's not true about it?
postgres=# SELECT 3 <@ '[3,7)'::int4rang
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/app-pgbasebackup.html
Description:
Hello.
On [this
page](https://www.postgresql.org/docs/current/app-pgbasebackup.html)
`spread` is mentioned:
-c {fast|spread}
--checkpoint={fast|spread}
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/rangetypes.html
Description:
Hi,
First I just wanted to say, the documentation is overall excellent, it has
been such a pleasure learning postgres.
In the RANGE types where it says the squ
On Mon, 2023-10-02 at 18:42 +, PG Doc comments form wrote:
> Page: https://www.postgresql.org/docs/16/functions-range.html
>
> The doc says:
> * unnest ( anymultirange ) → setof anyrange
> * Expands a multirange into a set of ranges. The ranges are read out in
> storage order (ascending).
>
>
Ok, but in section 3.5 I don't see examples on the "preceeding" clause.
What about enriching the section 3.5 then?
:
> Giampaolo Capelli writes:
> > I'd like to propose to add some examples to the following page
> > https://www.postgresql.org/docs/16/functions-window.html
>
> > The syntax of wi
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/functions-range.html
Description:
The doc says:
* unnest ( anymultirange ) → setof anyrange
* Expands a multirange into a set of ranges. The ranges are read out in
storage order (ascending
10 matches
Mail list logo
