On Tue, Mar 22, 2022 at 12:53 PM Matthias Kurz wrote:
> Hi everyone!
>
> I am watching this thread since quite a while and I am waiting eagerly a
> long time already that this feature finally lands in PostgreSQL.
> Given that in around 2 weeks PostgreSQL 15 will go into feature freeze (in
> the l
On Tue, Mar 22, 2022 at 5:32 PM Andrew Dunstan wrote:
>
> On 3/22/22 09:28, Oleg Bartunov wrote:
> >
> >
> > On Tue, Mar 22, 2022 at 12:53 PM Matthias Kurz
> > wrote:
> >
> > Hi everyone!
> >
> > I am watching this thread since quit
On Tue, Dec 15, 2020 at 8:01 PM Simon Riggs wrote:
>
> On Fri, 17 Jul 2020 at 21:26, Nikita Glukhov wrote:
> >
> > Attached 50th version of the patches. Only the documentation was changed
> > since the previous version.
>
> I can imagine the effort required to get to v50, so I salute your efforts
On Tue, Dec 15, 2020 at 8:37 PM Pavel Stehule wrote:
>
>
>
> út 15. 12. 2020 v 18:00 odesílatel Simon Riggs napsal:
>>
>> On Fri, 17 Jul 2020 at 21:26, Nikita Glukhov wrote:
>> >
>> > Attached 50th version of the patches. Only the documentation was changed
>> > since the previous version.
>>
>>
On Fri, Feb 12, 2021 at 1:14 PM Peter Eisentraut
wrote:
>
> There is another snowball release out, and I have prepared a patch to
> integrate it. It's very big and mostly boring, so I'm not attaching it
> here, but you can see it at
>
> https://github.com/petere/postgresql/commit/d0aa6c2148bcef10
On Mon, Sep 7, 2020 at 7:50 PM Heikki Linnakangas wrote:
>
> On 07/09/2020 13:59, Pavel Borisov wrote:
> I suppose there is a big jump in integer value (whether signed or
> unsigned) as you cross from positive to negative floats, and then the
> sort order is reversed. I have no ide
Hi there !
What's about GSoC 2022 ?
Best regards,
Oleg
On Tue, Apr 20, 2021 at 4:38 AM Andreas 'ads' Scherbaum wrote:
>
> Hello,
>
> On Sat, Apr 17, 2021 at 8:42 PM Nhi Dang wrote:
>
>>
>>
> Thank you for this document.
>
> It looks like there are a couple problems with this - at least if thi
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
On Mon, Apr 2, 2018 at 9:45 AM, Arthur Zakirov wrote:
> Hello Dmitry,
>
> Dmitry Dolgov <9erthali...@gmail.com> wrote:
>>
>> Any opinions about this suggestion? Can it be considered as a bug fix and
>> included into t
On Tue, Sep 1, 2015 at 12:33 PM Alexander Korotkov
wrote:
>
> Hi, Tomas!
>
> On Mon, Aug 31, 2015 at 6:26 PM, Tomas Vondra
> wrote:
>>
>> On 08/31/2015 09:41 AM, Anastasia Lubennikova wrote:
>>>
>>> I'm going to begin work on effective storage of duplicate keys in B-tree
>>> index.
>>> The main
On Wed, Sep 4, 2019 at 12:22 PM Andrey Borodin wrote:
>
> Hi, Peter! Thanks for looking into this.
>
> > 4 сент. 2019 г., в 14:09, Peter Eisentraut
> > написал(а):
> >
> > On 2019-06-24 10:44, Andrey Borodin wrote:
> >>> 18 мая 2019 г., в 11:44, Andrey Borodin написал(а):
> >>>
> >> Hi!
> >> He
On Fri, 22 Mar 2019, 03:14 Nikita Glukhov, wrote:
> Hi.
>
> Attached patch enables throwing of errors in jsonb_path_match() in its
> non-silent mode when the jsonpath expression failed to return a singleton
> boolean. Previously, NULL was always returned, and it seemed to be
> inconsistent with
On Tue, Jan 2, 2018 at 10:47 AM, Pavel Stehule wrote:
>
>
> 2018-01-02 3:04 GMT+01:00 Nikita Glukhov :
>>
>> On 29.11.2017 05:24, Michael Paquier wrote:
>>
>>> On Wed, Nov 15, 2017 at 10:17 AM, Nikita Glukhov
>>> wrote:
Attached the new version of the patches where displaying of SQL/JSO
On Tue, Jan 2, 2018 at 8:39 PM, Andrew Dunstan
wrote:
>
>
> On 01/02/2018 02:44 PM, Oleg Bartunov wrote:
>> On Tue, Jan 2, 2018 at 10:47 AM, Pavel Stehule
>> wrote:
>
>>> I am looking on this patch set and it looks very well.
>>>
>>> Personall
On 3 Jan 2018 00:23, "Andrew Dunstan"
wrote:
On 01/02/2018 05:04 PM, Nikita Glukhov wrote:
>
> I have removed all extra features from the patch set, they can be
> found in our
> github repository:
> https://github.com/postgrespro/sqljson/tree/sqljson_ext.
>
> Now there are 10 patches which have
On Sat, Jan 6, 2018 at 8:22 AM, Pavel Stehule wrote:
> Hi
>
> I am checking the JSONPath related code
>
> Questions, notes:
>
> 1. jsonpath operators are not consistent with any other .. json, xml .. I am
> missing ?, @> operátors
I have slides about jsonpath
http://www.sai.msu.su/~megera/postgre
On 9 Jan 2018 23:44, "Andrew Dunstan"
wrote:
On 01/02/2018 05:23 PM, Andrew Dunstan wrote:
>
> On 01/02/2018 05:04 PM, Nikita Glukhov wrote:
>> I have removed all extra features from the patch set, they can be
>> found in our
>> github repository:
>> https://github.com/postgrespro/sqljson/tree/
On 10 Jan 2018 20:14, "Andrew Dunstan"
wrote:
On 01/10/2018 01:37 AM, Oleg Bartunov wrote:
>
>
>
> this. Something similar to what we're using for json itself (a
> simple lexer and a recursive descent parser) would be more
> suitable.
&
On Wed, Feb 14, 2018 at 2:04 AM, Nikita Glukhov wrote:
> Attached 9th version of jsonpath patches rebased onto the latest master.
>
> Jsonpath grammar for parenthesized expressions and predicates was fixed.
>
> Documentation drafts for jsonpath written by Oleg Bartunov:
>
Bruce,
I noticed that jsonpath in your version is mentioned only in functions
chapter, but commit
72b6460336e86ad5cafd3426af6013c7d8457367 is about implementation of
SQL-2016 standard. We implemented JSON Path language as a jsonpath
datatype with a bunch of support functions, our implementation
s
On Mon, May 13, 2019 at 6:52 AM Bruce Momjian wrote:
>
> On Sun, May 12, 2019 at 09:49:40AM -0400, Bruce Momjian wrote:
> > On Sun, May 12, 2019 at 10:00:38AM +0300, Oleg Bartunov wrote:
> > > Bruce,
> > >
> > > I noticed that jsonpath in your version is me
Hello,
The commit 9b5c8d45f62bd3d243a40cc84deb93893f2f5122 is now 10+ years
old, may be we could remove deprecated @@@ operator ?
Author: Tom Lane
Date: Mon Apr 14 17:05:34 2008 +
Push index operator lossiness determination down to GIST/GIN opclass
"consistent" functions, and re
On Sun, Oct 21, 2018 at 11:24 PM Tom Lane wrote:
>
> Oleg Bartunov writes:
> > The commit 9b5c8d45f62bd3d243a40cc84deb93893f2f5122 is now 10+ years
> > old, may be we could remove deprecated @@@ operator ?
>
> Is it actually causing any problem? AFAICS it's just
On Mon, Oct 29, 2018 at 2:20 AM Tomas Vondra
wrote:
>
> Hi,
>
> On 10/02/2018 04:33 AM, Michael Paquier wrote:
> > On Sat, Sep 08, 2018 at 02:21:27AM +0300, Nikita Glukhov wrote:
> >> Attached 18th version of the patches rebased onto the current master.
> >
> > Nikita, this version fails to apply,
On Tue, Feb 20, 2018 at 12:01 AM, Arthur Zakirov
wrote:
> Thank you for your answer!
>
> 2018-02-19 18:43 GMT+03:00 Tom Lane :
>> We are not the upstream for the snowball stuff, and lack the expertise
>> to decide whether proposed changes are any good. To get anything
>> changed there, you'd have
On Mon, Feb 26, 2018 at 6:34 PM, Nikita Glukhov wrote:
> Attached 10th version of the jsonpath patches.
>
> 1. Fixed error handling in arithmetic operators.
>
>Now run-time errors in arithmetic operators are catched (added
>PG_TRY/PG_CATCH around operator's functions calls) and converted i
On Wed, Feb 28, 2018 at 5:46 PM, Nikolay Shaplov wrote:
> Concerning the patch that you've provided. I've just have a short look. But I
> already have some question.
>
> 1. I've seen you've added a new attribute into pg_index. Why??!!
> As far as I can get, if have index built on several columns
On Thu, Mar 1, 2018 at 7:02 PM, David Steele wrote:
> Hi Nikita,
>
> On 2/28/18 9:46 AM, Nikolay Shaplov wrote:
>> В письме от 28 февраля 2018 00:46:36 пользователь Nikita Glukhov написал:
>>
>>> I would like to present patch set implementing opclass parameters.
>>>
>>> This feature was recently p
On 2 Mar 2018 09:44, "Andres Freund" wrote:
Hi,
This patchset currently has multiple CF entries:
https://commitfest.postgresql.org/17/1063/
and then subordinate ones like
https://commitfest.postgresql.org/17/1471/
https://commitfest.postgresql.org/17/1472/
https://commitfest.postgresql.org/17/1
Thanks, Tomas !
Will publish a new version really soon !
Regards,
Oleg
On Tue, Mar 6, 2018 at 12:29 AM, Tomas Vondra
wrote:
> Hi,
>
> The patch no longer applies - it got broken by fd1a421fe66 which changed
> columns in pg_proc. A rebase is needed.
>
> Fixing it is pretty simle, so I've done th
On Tue, Mar 13, 2018 at 2:04 PM, Simon Riggs wrote:
> On 7 March 2018 at 14:34, Nikita Glukhov wrote:
>
>> Attached 12th version of SQL/JSON patches rebased onto the latest master.
>
> Please write some docs or notes to go with this.
>
> If you drop a big pile of code with no explanation it will
On 14 Mar 2018 01:54, "Michael Paquier" wrote:
On Tue, Mar 13, 2018 at 04:08:01PM +0300, Oleg Bartunov wrote:
> The docs are here
> https://github.com/obartunov/sqljsondoc/blob/master/README.jsonpath.md
>
> It's not easy to write docs for SQL/JSON in xml, so I decided
On 14 Mar 2018 17:11, "Alexander Korotkov"
wrote:
On Wed, Mar 14, 2018 at 2:10 AM, Andres Freund wrote:
> On 2018-03-14 07:54:35 +0900, Michael Paquier wrote:
> > On Tue, Mar 13, 2018 at 04:08:01PM +0300, Oleg Bartunov wrote:
> > > The docs are here
> &
On Wed, Apr 14, 2021 at 11:09 AM Pavel Stehule
wrote:
>
>
> st 14. 4. 2021 v 9:57 odesílatel Dmitry Dolgov <9erthali...@gmail.com>
> napsal:
>
>> > On Wed, Apr 14, 2021 at 09:20:08AM +0200, Pavel Stehule wrote:
>> > st 14. 4. 2021 v 7:39 odesílatel Joel Jacobson
>> napsal:
>> >
>> > > Hi,
>> > >
&
> Kraska, T. (2020, June). ALEX: an updatable adaptive learned index. In
> Proceedings of the 2020 ACM SIGMOD International Conference on
> Management of Data (pp. 969-984). Web access:
> https://doi.org/10.1145/3318464.3389711 /
> https://dblp.org/rec/conf/sigmod/DingMYWDLZC
On Tue, Jun 16, 2020 at 4:53 PM Tom Lane wrote:
> Peter Eisentraut writes:
> > There are two cases where these two columns are not the same:
>
> > hindi english \
> > russian english \
>
> > The second one is old; the first one I added using the second one as
> > exam
On Wed, Jun 17, 2020 at 6:33 PM Tom Lane wrote:
> Alexander Korotkov writes:
> > On Thu, Jun 11, 2020 at 10:00 PM Tom Lane wrote:
> >> I don't think this is very relevant. The SQL standard has not got the
> >> concepts of Inf or NaN either (see 4.4.2 Characteristics of numbers),
> >> therefore
On Fri, May 22, 2020 at 5:11 PM Tom Lane wrote:
> Peter Eisentraut writes:
> > Snowball has made a release! With a tag!
> > I have prepared a patch to update PostgreSQL's copy.
>
> Yeah, this was on my to-do list as well. Thanks for doing it.
>
+1
>
> > I think some consideration could be g
On Mon, Jan 21, 2019 at 1:40 AM Alexander Korotkov
wrote:
>
> On Sun, Jan 20, 2019 at 6:30 AM Alexander Korotkov
> wrote:
> > I'll continue revising this patchset. Nikita, could you please write
> > tests for 3-argument versions of functions? Also, please answer the
> > question regarding "id"
On Tue, Jan 22, 2019 at 8:21 AM Alexander Korotkov
wrote:
>
> The next revision is attached.
>
> Nikita made code and documentation improvements, renamed functions
> from "jsonpath_" prefix to "jsonb_path_" prefix. He also renamed
> jsonpath_predicate() to jsonb_path_match() (that looks better fo
On Sun, Dec 2, 2018 at 1:25 AM Tatsuo Ishii wrote:
>
> In the documentation of ssl_passphrase_command_supports_reload:
>
> configuration reload if a key file needs a passphrase. If this
> parameter is false (the default), then
> :
> :
> running. Setting this parameter to
On Sat, 1 Jun 2019, 16:41 Chapman Flack, wrote:
> Hi,
>
> We had a short conversation about this on Friday but I didn't have time
> to think of a constructive suggestion, and now I've had more time to
> think about it.
>
> Regarding the proposed PG 13 jsonpath extensions (array, map, and
> sequen
On Fri, Jun 28, 2019 at 8:10 AM Alvaro Herrera wrote:
>
> On 2019-Jun-28, Alexander Korotkov wrote:
>
> > On Tue, Jun 25, 2019 at 6:38 PM Liudmila Mantrova
> > wrote:
> > > Thank you for the catch! Please see the modified version of patch 0004
> > > attached.
> >
> > I tried to review and revise
On Mon, Jul 8, 2019 at 7:22 AM Thomas Munro wrote:
>
> On Sun, Apr 7, 2019 at 3:46 AM Tom Lane wrote:
> > =?UTF-8?Q?Filip_Rembia=C5=82kowski?= writes:
> > > Here is my attempt to fix a 12-years old ltree bug (which is a todo item).
> > > I see it's not backward-compatible, but in my understandin
On 14 Nov 2017 11:35, "Anthony Bykov" wrote:
On Fri, 10 Nov 2017 14:40:21 +0100
Pavel Stehule wrote:
> Hi
>
> 2017-10-24 14:27 GMT+02:00 Anthony Bykov :
>
> > There are some moments I should mention:
> > 1. {"1":1}::jsonb is transformed into HV {"1"=>"1"}, while
> > ["1","2"]::jsonb is transfor
On Thu, Nov 23, 2017 at 6:01 PM, Peter Eisentraut
wrote:
> The documentation sources are now DocBook XML, not SGML. (The files are
> still named *.sgml. That's something to think about separately.)
Congratulations to you and Alexander ! That is what I waited for a long time.
Now we could think
On Mon, Dec 11, 2017 at 11:11 PM, Nikolay Samokhvalov
wrote:
> Very interesting read: https://arxiv.org/abs/1712.01208
>
> HN discussion: https://news.ycombinator.com/item?id=15894896
>
> Some of the comments (from Twitter
> https://twitter.com/schrockn/status/940037656494317568): "Jeff Dean and c
On Tue, Dec 12, 2017 at 6:07 PM, Alexander Korotkov
wrote:
> Hi!
>
> Let me add my two cents too.
>
> On Tue, Dec 12, 2017 at 2:41 PM, Ildus Kurbangaliev
> wrote:
>>
>> On Mon, 11 Dec 2017 20:53:29 +0100 Tomas Vondra
>> wrote:
>> > Replacing the algorithm used to compress all varlena values (in
On Fri, Dec 15, 2017 at 10:49 PM, Gene Selkov wrote:
> Greetings everyone,
Привет !
>
> I need a data type to represent genomic positions, which will consist of a
> string and a pair of integers with interval logic and access methods. Sort
> of like my seg type, but more straightforward.
Why no
48 matches
Mail list logo