On Sun, Dec 20, 2020 at 9:06 AM Erik Rijkers wrote:
> On 2020-12-20 05:21, Alexander Korotkov wrote:
> > Multirange datatypes
> >
> > Multiranges are basically sorted arrays of non-overlapping ranges with
> > set-theoretic operations defined over them.
> >
>
> With --enable-cassert gcc 10.1.0 gi
Fix compiler warning introduced in 6df7a9698b
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/11072e86939d2f5ca0a97c709b46f29ea8b57590
Modified Files
--
src/backend/commands/typecmds.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Sun, Dec 20, 2020 at 4:18 PM Alexander Korotkov wrote:
> On Sun, Dec 20, 2020 at 9:06 AM Erik Rijkers wrote:
> > On 2020-12-20 05:21, Alexander Korotkov wrote:
> > > Multirange datatypes
> > >
> > > Multiranges are basically sorted arrays of non-overlapping ranges with
> > > set-theoretic oper
On 2020-12-20 14:18, Alexander Korotkov wrote:
On Sun, Dec 20, 2020 at 9:06 AM Erik Rijkers wrote:
On 2020-12-20 05:21, Alexander Korotkov wrote:
> Multirange datatypes
>
> Multiranges are basically sorted arrays of non-overlapping ranges with
> set-theoretic operations defined over them.
>
Wi
On Sun, Dec 20, 2020 at 8:16 AM Alexander Korotkov wrote:
> On Sun, Dec 20, 2020 at 8:06 AM Tom Lane wrote:
> > Alexander Korotkov writes:
> > > Multirange datatypes
> >
> > crake's not happy with this. Looks like you did not think through
> > what pg_dump has to do for back-branch servers.
>
>
Hi!
On Sun, Dec 20, 2020 at 4:37 PM Alexander Korotkov wrote:
>
> On Sun, Dec 20, 2020 at 8:16 AM Alexander Korotkov
> wrote:
> > On Sun, Dec 20, 2020 at 8:06 AM Tom Lane wrote:
> > > Alexander Korotkov writes:
> > > > Multirange datatypes
> > >
> > > crake's not happy with this. Looks like
Avoid memcpy() with same source and destination in pgstat_recv_replslot.
Same type of issue as in commit 53d4f5fef and earlier fixes; also
found by apparently-more-picky-than-the-buildfarm valgrind testing.
This one is an oversight in commit 986816750. Since that's new in
HEAD, no need for a back
Doc: improve description of pgbench script weights.
Point out the workaround to be used if you want to write a script
file name that includes "@". Clean up the text a little.
Fabien Coelho, additional wordsmithing by me
Discussion:
https://postgr.es/m/1c4e81550d214741827a0329db8d@G08CNEXMB
Doc: improve description of pgbench script weights.
Point out the workaround to be used if you want to write a script
file name that includes "@". Clean up the text a little.
Fabien Coelho, additional wordsmithing by me
Discussion:
https://postgr.es/m/1c4e81550d214741827a0329db8d@G08CNEXMB
Doc: improve description of pgbench script weights.
Point out the workaround to be used if you want to write a script
file name that includes "@". Clean up the text a little.
Fabien Coelho, additional wordsmithing by me
Discussion:
https://postgr.es/m/1c4e81550d214741827a0329db8d@G08CNEXMB
Doc: improve description of pgbench script weights.
Point out the workaround to be used if you want to write a script
file name that includes "@". Clean up the text a little.
Fabien Coelho, additional wordsmithing by me
Discussion:
https://postgr.es/m/1c4e81550d214741827a0329db8d@G08CNEXMB
Doc: improve description of pgbench script weights.
Point out the workaround to be used if you want to write a script
file name that includes "@". Clean up the text a little.
Fabien Coelho, additional wordsmithing by me
Discussion:
https://postgr.es/m/1c4e81550d214741827a0329db8d@G08CNEXMB
Doc: improve description of pgbench script weights.
Point out the workaround to be used if you want to write a script
file name that includes "@". Clean up the text a little.
Fabien Coelho, additional wordsmithing by me
Discussion:
https://postgr.es/m/1c4e81550d214741827a0329db8d@G08CNEXMB
On Sun, Dec 20, 2020 at 5:56 PM Alexander Korotkov wrote:
> On Sun, Dec 20, 2020 at 4:37 PM Alexander Korotkov
> wrote:
> > On Sun, Dec 20, 2020 at 8:16 AM Alexander Korotkov
> > wrote:
> > > On Sun, Dec 20, 2020 at 8:06 AM Tom Lane wrote:
> > > > Alexander Korotkov writes:
> > > > > Multira
Doc: fix description of how to use src/tutorial files.
The separate "cd" command before invoking psql made sense (or at least
I thought so) when it was added in commit ed1939332. But 4e3a61635
removed the supporting text that explained when to use it, making it
just confusing. So drop it.
Also
Doc: fix description of how to use src/tutorial files.
The separate "cd" command before invoking psql made sense (or at least
I thought so) when it was added in commit ed1939332. But 4e3a61635
removed the supporting text that explained when to use it, making it
just confusing. So drop it.
Also
Doc: fix description of how to use src/tutorial files.
The separate "cd" command before invoking psql made sense (or at least
I thought so) when it was added in commit ed1939332. But 4e3a61635
removed the supporting text that explained when to use it, making it
just confusing. So drop it.
Also
Doc: fix description of how to use src/tutorial files.
The separate "cd" command before invoking psql made sense (or at least
I thought so) when it was added in commit ed1939332. But 4e3a61635
removed the supporting text that explained when to use it, making it
just confusing. So drop it.
Also
Doc: fix description of how to use src/tutorial files.
The separate "cd" command before invoking psql made sense (or at least
I thought so) when it was added in commit ed1939332. But 4e3a61635
removed the supporting text that explained when to use it, making it
just confusing. So drop it.
Also
Doc: fix description of how to use src/tutorial files.
The separate "cd" command before invoking psql made sense (or at least
I thought so) when it was added in commit ed1939332. But 4e3a61635
removed the supporting text that explained when to use it, making it
just confusing. So drop it.
Also
Doc: fix description of how to use src/tutorial files.
The separate "cd" command before invoking psql made sense (or at least
I thought so) when it was added in commit ed1939332. But 4e3a61635
removed the supporting text that explained when to use it, making it
just confusing. So drop it.
Also
Fix typalign in rangetypes statistics
6df7a9698b introduces multirange types, whose typanalyze function shares
infrastructure with range types typanalyze function. Since 6df7a9698b,
information about type gathered by statistics is filled from typcache.
But typalign is mistakenly always set to dou
Refactor logic to check for ASCII-only characters in string
The same logic was present for collation commands, SASLprep and
pgcrypto, so this removes some code.
Author: Michael Paquier
Reviewed-by: Stephen Frost, Heikki Linnakangas
Discussion: https://postgr.es/m/[email protected]
Bra
Hi
On Mon, Dec 21, 2020 at 1:32 AM Alexander Korotkov
wrote:
> On Sun, Dec 20, 2020 at 5:56 PM Alexander Korotkov
> wrote:
> > On Sun, Dec 20, 2020 at 4:37 PM Alexander Korotkov
> wrote:
> > > On Sun, Dec 20, 2020 at 8:16 AM Alexander Korotkov <
> [email protected]> wrote:
> > > > On Sun, D
Hi Alexander,
On Sun, Dec 20, 2020 at 04:21:16AM +, Alexander Korotkov wrote:
> Multirange datatypes
>
> Multiranges are basically sorted arrays of non-overlapping ranges with
> set-theoretic operations defined over them.
This commit is creating a compilation warning on Windows:
multirangety
25 matches
Mail list logo
