Re: [HACKERS] WIP: Upper planner pathification

On Tue, Mar 1, 2016 at 3:11 PM, Teodor Sigaev wrote: > The basic point of this patch is to apply the generate-and-compare-Paths >> paradigm to the planning steps after query_planner(), which only covers >> > ... > > The present patch addresses this problem by inventing Path nodes to > > represent

Re: [HACKERS] The plan for FDW-based sharding

On Tue, Mar 1, 2016 at 7:03 PM, Robert Haas wrote: > On Tue, Mar 1, 2016 at 10:37 AM, Bruce Momjian wrote: > > On Tue, Mar 1, 2016 at 10:19:45AM -0500, Robert Haas wrote: > >> > Two reasons: > >> > 1. There is no ideal implementation of DTM which will fit all > possible needs > >> > and be eff

Re: [HACKERS] The plan for FDW-based sharding

On Wed, Mar 2, 2016 at 4:36 AM, Tomas Vondra wrote: Hi, > > On 03/01/2016 08:02 PM, Bruce Momjian wrote: > >> On Tue, Mar 1, 2016 at 07:56:58PM +0100, Petr Jelinek wrote: >> >>> Note that I am not saying that other discussed approaches are any >>> better, I am saying that we should know approxim

Re: [HACKERS] The plan for FDW-based sharding

On Mar 3, 2016 4:47 AM, "Michael Paquier" wrote: > > On Wed, Mar 2, 2016 at 6:54 PM, Alexander Korotkov > wrote: > > If FDWs existed then Postgres XC/XL were being developed then I believe they > > would try to build full-featured prototype of FDW based sharding. If this > > prototype succeed the

Re: [HACKERS] SP-GiST support for inet datatypes

On Wed, Mar 2, 2016 at 11:56 PM, Emre Hasegeli wrote: > Attached patches add SP-GiST support to the inet datatypes. The operator > class comes with a small change on the SP-GiST framework to allow fixed > number of child nodes. > > The index is like prefix tree except that it doesn't bother to s

Re: [HACKERS] SP-GiST support for inet datatypes

On Thu, Mar 3, 2016 at 8:51 AM, Oleg Bartunov wrote: > > > On Wed, Mar 2, 2016 at 11:56 PM, Emre Hasegeli wrote: > >> Attached patches add SP-GiST support to the inet datatypes. The >> operator class comes with a small change on the SP-GiST framework to allow >&g

Re: [HACKERS] The plan for FDW-based sharding

On Tue, Mar 8, 2016 at 6:40 AM, Craig Ringer wrote: > Either that, or bless experimental features/API as an official concept. > I'd quite like that myself - stuff that's in Pg, but documented as "might > change or go away in the next release, experimental feature". As we're > doing more stuff t

Re: [HACKERS] SP-GiST support for inet datatypes

On Thu, Mar 3, 2016 at 11:45 AM, Emre Hasegeli wrote: > > Emre, I checked original thread and didn't find sample data. Could you > provide them for testing ? > > I found it on the Git history: > > > https://github.com/job/irrexplorer/blob/9e8b5330d7ef0022abbe1af18291257e044eb24b/data/irrexplorer_

Re: [HACKERS] SP-GiST support for inet datatypes

On Tue, Mar 8, 2016 at 11:17 PM, Oleg Bartunov wrote: > > > On Thu, Mar 3, 2016 at 11:45 AM, Emre Hasegeli wrote: > >> > Emre, I checked original thread and didn't find sample data. Could you >> provide them for testing ? >> >> I found it on the

Re: [HACKERS] The plan for FDW-based sharding

On Fri, Mar 11, 2016 at 9:09 AM, Bruce Momjian wrote: > > > > 3. I have tried to encourage others to get involved, with limited > success. I do think the FDW is perhaps the only reasonable way to get > _built-in_ sharding. The external sharding solutions are certainly > viable, but external.

Re: [HACKERS] WIP: Access method extendability

On Wed, Mar 9, 2016 at 8:31 PM, Alexander Korotkov < a.korot...@postgrespro.ru> wrote: > Hi! > > On Wed, Mar 9, 2016 at 3:27 PM, Alvaro Herrera > wrote: > >> Hi. As I just said to Tomas Vondra: since your patch creates a new >> object type, please make sure to add a case to cover it in the >> ob

Re: [HACKERS] eXtensible Transaction Manager API (v2)

On Fri, Mar 11, 2016 at 7:11 PM, David Steele wrote: > On 2/10/16 12:50 PM, Konstantin Knizhnik wrote: > > > PostgresProffesional cluster teams wants to propose new version of > > eXtensible Transaction Manager API. > > Previous discussion concerning this patch can be found here: > > > > > http:/

Re: [HACKERS] Background Processes and reporting

On Sat, Mar 12, 2016 at 12:45 AM, Andres Freund wrote: > On 2016-03-12 02:24:33 +0300, Alexander Korotkov wrote: > > > > So, situation looks like dead-end. I have no idea how to convince Robert > > about any kind of advanced functionality of wait monitoring to > PostgreSQL. > > I'm thinking abo

Re: [HACKERS] [PATCH] we have added support for box type in SP-GiST index

On Mon, Mar 14, 2016 at 9:01 PM, David Steele wrote: > On 2/15/16 10:29 AM, Teodor Sigaev wrote: > > It's very pity but author is not able to continue work on this patch, >> and I would like to raise this flag. >> >> I'd like to add some comments about patches: >> >> traversalValue patch adds arb

Re: [HACKERS] Background Processes and reporting

On Tue, Mar 15, 2016 at 7:43 PM, Alexander Korotkov < a.korot...@postgrespro.ru> wrote: > On Tue, Mar 15, 2016 at 12:57 AM, Robert Haas > wrote: > >> On Mon, Mar 14, 2016 at 4:42 PM, Andres Freund >> wrote: >> > On 2016-03-14 16:16:43 -0400, Robert Haas wrote: >> >> > I have already shown [0, 1]

Re: [HACKERS] Bug in searching path in jsonb_set when walking through JSONB array

On Wed, Mar 23, 2016 at 6:37 AM, Vitaly Burovoy wrote: > Hello, Hackers! > > While I was reviewed a patch with "json_insert" function I found a bug > which wasn't connected with the patch and reproduced at master. > > It claims about non-integer whereas input values are obvious integers > and in

Re: [HACKERS] Draft release notes for next week's releases

On Mar 28, 2016 09:44, "Peter Geoghegan" wrote: > > On Sat, Mar 26, 2016 at 4:34 PM, Tom Lane wrote: > > Probably the most discussion-worthy item is whether we can say > > anything more about the strxfrm mess. Should we make a wiki > > page about that and have the release note item link to it? >

Re: [HACKERS] Draft release notes for next week's releases

On Mon, Mar 28, 2016 at 1:21 PM, Peter Geoghegan wrote: > On Mon, Mar 28, 2016 at 12:08 AM, Oleg Bartunov > wrote: > > Should we start thinking about ICU ? I compare Postgres with ICU and > without > > and found 27x improvement in btree index creation for russian strings

Re: [HACKERS] Draft release notes for next week's releases

On Mon, Mar 28, 2016 at 2:06 PM, Peter Geoghegan wrote: > On Mon, Mar 28, 2016 at 12:55 AM, Oleg Bartunov > wrote: > > We'll post the patch. > > Cool. > > > Teodor made something to get abbreviated keys work as > > I remember. I should say, that 27x imp

Re: [HACKERS] Dealing with collation and strcoll/strxfrm/etc

On Mon, Mar 28, 2016 at 5:57 PM, Stephen Frost wrote: > All, > > Changed the thread name (we're no longer talking about release > notes...). > > * Tom Lane (t...@sss.pgh.pa.us) wrote: > > Oleg Bartunov writes: > > > Should we start thinking about ICU ? >

Re: [HACKERS] Draft release notes for next week's releases

On Mon, Mar 28, 2016 at 1:36 PM, Thomas Kellerer wrote: > Oleg Bartunov-2 wrote > > But still, icu provides us abbreviated keys and collation stability, > > Does include ICU mean that collation handling is identical across > platforms? > E.g. a query on Linux involving st

Re: [HACKERS] Draft release notes for next week's releases

On Mon, Mar 28, 2016 at 6:08 PM, Robert Haas wrote: > On Mon, Mar 28, 2016 at 10:24 AM, Tom Lane wrote: > > I'm also not exactly convinced by your implicit assumption that ICU is > > bug-free. > > Noah spent some time looking at ICU back when he was EnterpriseDB, and > his conclusion was that I

Re: [HACKERS] New committer

On Thu, Jan 28, 2016 at 5:37 PM, Magnus Hagander wrote: > Hello! > > The PostgreSQL core team would like to welcome Dean Rasheed as a new > committer for the PostgreSQL project. > > Dean - welcome! Now let's see how quickly you can break the buildfarm! > Congratulations, of course ! I'd like to

[HACKERS] thanks for FOSDEM/PGDay 2016 Developer Meeting

I read https://wiki.postgresql.org/wiki/FOSDEM/PGDay_2016_Developer_Meeting and would like to say thanks for such nice review of meeting. Oleg

Re: [HACKERS] Fuzzy substring searching with the pg_trgm extension

On Fri, Jan 29, 2016 at 1:11 PM, Alvaro Herrera wrote: > Artur Zakirov wrote: > > > What status of this patch? In commitfest it is "Needs review". > > "Needs review" means it needs a reviewer to go over it and, uh, review > it. Did I send an email to you prodding you to review patches? I sent >

Re: [HACKERS] [PATCH] Phrase search ported to 9.6

On Tue, Feb 2, 2016 at 10:18 AM, Andreas Joseph Krogh wrote: > På tirsdag 02. februar 2016 kl. 04:22:57, skrev Michael Paquier < > michael.paqu...@gmail.com>: > > > > On Mon, Feb 1, 2016 at 8:21 PM, Dmitry Ivanov > wrote: >> >> This patch was origina

Re: [HACKERS] [PATCH] Phrase search ported to 9.6

On Tue, Feb 2, 2016 at 2:04 PM, Alvaro Herrera wrote: > Andreas Joseph Krogh wrote: > > > Which seems to indicate it has received a fair amount of testing and is > quite > > stable. > > Hopefully it integrates into the 9.6 codebase without too much risk. > > Yes, yes, that's all very good, but we

[HACKERS] old bug in full text parser

It looks like there is a very old bug in full text parser (somebody pointed me on it), which appeared after moving tsearch2 into the core. The problem is in how full text parser process hyphenated words. Our original idea was to report hyphenated word itself as well as its parts and ignore hyphen

Re: [HACKERS] old bug in full text parser

On Wed, Feb 10, 2016 at 12:28 PM, Oleg Bartunov wrote: > It looks like there is a very old bug in full text parser (somebody > pointed me on it), which appeared after moving tsearch2 into the core. The > problem is in how full text parser process hyphenated words. Our original >

Re: [HACKERS] old bug in full text parser

On Wed, Feb 10, 2016 at 7:45 PM, Mike Rylander wrote: > On Wed, Feb 10, 2016 at 4:28 AM, Oleg Bartunov > wrote: > > It looks like there is a very old bug in full text parser (somebody > pointed > > me on it), which appeared after moving tsearch2 into the core. The > pr

Re: [HACKERS] old bug in full text parser

On Wed, Feb 10, 2016 at 7:21 PM, Tom Lane wrote: > Oleg Bartunov writes: > > It looks like there is a very old bug in full text parser (somebody > > pointed me on it), which appeared after moving tsearch2 into the core. > The > > problem is in how full text parser proce

Re: [HACKERS] [WIP] ALTER ... OWNER TO ... CASCADE

On Mon, Feb 15, 2016 at 7:25 PM, Tom Lane wrote: > Teodor Sigaev writes: > >> So basically, a generic CASCADE facility sounds like a lot of work to > >> produce something that would seldom be anything but a foot-gun. > > > DELETE FROM or TRUNCATE could be a foot-gun too, but it's not a reason >

[HACKERS] commitfest problem ?

This entry https://commitfest.postgresql.org/8/419/ contains very unrelated patches from another commitfest. I think Oleg

Re: [HACKERS] pglogical - logical replication contrib module

On Tue, Feb 16, 2016 at 5:38 PM, Bruce Momjian wrote: > On Tue, Jan 26, 2016 at 08:14:26PM -0800, Joshua Drake wrote: > > On 12/31/2015 03:34 PM, Petr Jelinek wrote: > > >Hi, > > > > > >I'd like to submit the replication solution which is based on the > > >pglogical_output [1] module (which is ob

Re: [HACKERS] tsearch_extras extension

On Wed, Feb 17, 2016 at 6:57 AM, Tim Abbott wrote: > Just following up here since I haven't gotten a reply -- I'd love to work > with someone from the Postgres community on a plan to make the > tsearch_extras functionality available as part of mainline postgres. > > > -Tim Abbott > > On W

Re: [HACKERS] Figures in docs

On Wed, Feb 17, 2016 at 4:17 AM, Tatsuo Ishii wrote: > It seems there's no figures/diagrams in our docs. I vaguely recall that > we used to have a few diagrams in our docs. If so, was there any > technical reason to remove them? > I don't know the reason, but it's shame, we are still in sgml !

Re: [HACKERS] [WIP] speeding up GIN build with parallel workers

On Wed, Feb 17, 2016 at 6:55 PM, Constantin S. Pan wrote: > On Sat, 16 Jan 2016 01:38:39 +0300 > "Constantin S. Pan" wrote: > > > The task of building GIN can require lots of time and eats 100 % CPU, > > but we could easily make it use more than a 100 %, especially since we > > now have parallel

Re: [HACKERS] The plan for FDW-based sharding

On Wed, Feb 24, 2016 at 12:17 PM, Alexander Korotkov < a.korot...@postgrespro.ru> wrote: > Hi, Bruce! > > The important point for me is to distinguish different kind of plans: > implementation plan and research plan. > If we're talking about implementation plan then it should be proven that > prop

Re: [HACKERS] The plan for FDW-based sharding

On Fri, Feb 26, 2016 at 3:50 PM, Robert Haas wrote: > On Wed, Feb 24, 2016 at 3:05 PM, Oleg Bartunov > wrote: > > I already several times pointed, that we need XTM to be able to continue > > development in different directions, since there is no clear winner. > > Moreo

[HACKERS] Fwd: [Snowball-discuss] Greek stemmer

This is a chance to add default configuration for Greek language if somebody with good knowledge could follow this development. Oleg -- Forwarded message -- From: Oleg Smirnov Date: Thu, Aug 25, 2016 at 5:26 PM Subject: [Snowball-discuss] Greek stemmer To: "snowball-discu." Hi

Re: [HACKERS] Better tracking of free space during SP-GiST index build

On Sat, Sep 24, 2016 at 11:32 PM, Tomas Vondra wrote: > On 09/22/2016 07:37 PM, Tom Lane wrote: >> >> Tomas Vondra writes: >> >>> ... I've tried increasing the cache size to 768 >>> entries, with vast majority of them (~600) allocated to leaf pages. >>> Sadly, this seems to only increase the CREA

Re: [HACKERS] How to implement a SP-GiST index as a extension module?

On Sun, Oct 29, 2017 at 10:07 AM, Connor Wolf wrote: > Hi there! > > I'm looking at implementing a custom indexing scheme, and I've been having > trouble understanding the proper approach. > > Basically, I need a BK tree, which is a tree-structure useful for indexing > arbitrary discrete metric-sp

Re: [HACKERS] How to implement a SP-GiST index as a extension module?

On Mon, Oct 30, 2017 at 12:05 PM, Oleg Bartunov wrote: > On Sun, Oct 29, 2017 at 10:07 AM, Connor Wolf > wrote: >> Hi there! >> >> I'm looking at implementing a custom indexing scheme, and I've been having >> trouble understanding the proper approach. >

Re: [HACKERS] Custom compression methods

On Thu, Nov 2, 2017 at 6:02 PM, Craig Ringer wrote: > On 2 November 2017 at 17:41, Ildus Kurbangaliev > wrote: > >> In this patch compression methods is suitable for MAIN and EXTENDED >> storages like in current implementation in postgres. Just instead only >> of LZ4 you can specify any other com

Re: [HACKERS] need info about extensibility in other databases

On Wed, Nov 8, 2017 at 2:37 PM, Li Song wrote: > Hi, > > When is the English version of "GiST programming tutorial" available? Well, I wrote it many years ago, so it needs to be updated. For now, you can use google translate, which seems works fine https://translate.google.com/translate?sl=auto&t

Re: [HACKERS] [PATCH] Generic type subscription

On Sat, Oct 1, 2016 at 12:52 PM, Dmitry Dolgov <9erthali...@gmail.com> wrote: > > I've tried to compile this patch with current state of master (commit > > 51c3e9fade76c12) and found out that, when configured with > --enable-cassert, > > it doesn't pass make check. > > Thanks for the feedback. Ye

Re: [HACKERS] [PATCH] Generic type subscription

On Wed, Oct 5, 2016 at 6:48 AM, Dmitry Dolgov <9erthali...@gmail.com> wrote: > On 5 October 2016 at 03:00, Oleg Bartunov wrote: > >> >> have you ever run 'make check' ? >> >> = >> 53 of 168 tests failed. >>

Re: [HACKERS] [PATCH] few fts functions for jsonb

The proposed patch looks not very important, but I consider it as an important feature, which Oracle and Microsoft already have, that's why I asked Dmitry to work on this and made it before feature freeze. My comments follows below the post. On Tue, Feb 28, 2017 at 1:59 PM, Dmitry Dolgov <9erthali

[HACKERS] SQL/JSON in PostgreSQL

- the often requested feature by the users. The patch is consists of about 15000 insertions (about 5000 lines are from tests), passes all regression tests and doesn’t touches critical parts, so we hope with community help to bring it to committable state. Authors: Nikita Glukhov, Teodor Sigaev,

Re: [HACKERS] SQL/JSON in PostgreSQL

On Tue, Feb 28, 2017 at 10:55 PM, Pavel Stehule wrote: > Hi > > > 2017-02-28 20:08 GMT+01:00 Oleg Bartunov : > >> Hi there, >> >> >> Attached patch is an implementation of SQL/JSON data model from SQL-2016 >> standard (ISO/IEC 9075-2:2016(E)), which

Re: [HACKERS] SQL/JSON in PostgreSQL

On Fri, Mar 3, 2017 at 11:49 PM, David Steele wrote: > Hi Oleg, > > On 2/28/17 2:55 PM, Pavel Stehule wrote: > > 2017-02-28 20:08 GMT+01:00 Oleg Bartunov > > > Attached patch is an implementation of SQL/JSON data model from > > SQL-2016 standard (ISO/

Re: [HACKERS] SQL/JSON in PostgreSQL

On Wed, Mar 8, 2017 at 12:43 AM, Sven R. Kunze wrote: > Hi, > > about the datetime issue: as far as I know, JSON does not define a > serialization format for dates and timestamps. > > On the other hand, YAML (as a superset of JSON) already supports a > language-independent date(time) serializatio

Re: [HACKERS] SQL/JSON in PostgreSQL

On Wed, Mar 8, 2017 at 7:05 AM, David Steele wrote: > On 3/7/17 11:38 AM, Andres Freund wrote: > > <...> > > We have a plenty of time and we dedicate one full-time developer for >>> this project. >>> >> >> How about having that, and perhaps others, developer participate in >> reviewing patches an

Re: [HACKERS] SQL/JSON in PostgreSQL

On Fri, Mar 10, 2017 at 7:07 AM, Petr Jelinek wrote: > On 09/03/17 19:50, Peter van Hardenberg wrote: > > Anecdotally, we just stored dates as strings and used a convention (key > > ends in "_at", I believe) to interpret them. The lack of support for > > dates in JSON is well-known, universally d

Re: [HACKERS] SQL/JSON in PostgreSQL

On Mon, Mar 13, 2017 at 9:24 AM, Nico Williams wrote: > On Thu, Mar 09, 2017 at 07:12:07PM +0100, Sven R. Kunze wrote: > > From my day-to-day work I can tell, the date(time) type is the only > missing > > piece of JSON to make it perfect for business applications (besides, > maybe, > > a "currenc

Re: [HACKERS] Why is it "JSQuery"?

People, we have many other tasks than guessing the language name. jsquery is just an extension, which we invent to test our indexing stuff. Eventually, it grew out. I think we'll think on better name if developers agree to have it in core. For now, jsquery is good enough to us. jsquery name doe

Re: [HACKERS] Why is it "JSQuery"?

The closest problem we have is jsonb statistics (lack of, actually) , which prevents use of all the power of jsquery. I hope Jan Urbański could work on this. Oleg On Tue, Jun 10, 2014 at 11:06 PM, Oleg Bartunov wrote: > People, > > we have many other tasks than guessing the lang

Re: [HACKERS] Minmax indexes

+1 for BRIN ! On Thu, Aug 7, 2014 at 6:16 PM, Simon Riggs wrote: > On 7 August 2014 14:53, Robert Haas wrote: >> On Wed, Aug 6, 2014 at 4:06 PM, Nicolas Barbier >> wrote: >>> 2014-08-06 Claudio Freire : >>> So, I like blockfilter a lot. I change my vote to blockfilter ;) >>> >>> +1 for blo

Re: [HACKERS] jsonb format is pessimal for toast compression

I did quick test on the same bookmarks to test performance of 9.4beta2 and 9.4beta2+patch The query was the same we used in pgcon presentation: SELECT count(*) FROM jb WHERE jb @> '{"tags":[{"term":"NYC"}]}'::jsonb; table size | time (ms) 9.4beta2:1374 Mb

Re: [HACKERS] [GSoC] Push-based query executor discussion

On Wed, Mar 22, 2017 at 8:04 PM, Arseny Sher wrote: > > While I admire your fearlessness, I think the chances of you being > > able to bring a project of this type to a successful conclusion are > > remote. Here is what I said about this topic previously: > > > > http://postgr.es/m/CA+Tgmoa=kzHJ

Re: [HACKERS] [PATCH] few fts functions for jsonb

On 30 Mar 2017 23:43, "Dmitry Dolgov" <9erthali...@gmail.com> wrote: On 31 March 2017 at 00:01, Andrew Dunstan wrote: > > I have just noticed as I was writing/testing the non-existent docs for > this patch that it doesn't supply variants of to_tsvector that take a > regconfig as the first argumen

Re: [HACKERS] [PATCH] Pageinspect - add functions on GIN and GiST indexes from gevel

GIN and GiST indexes to pageinspect. Gevel was originally >> designed by Oleg Bartunov, and Teodor Sigaev for developers of GiST and >> GIN indexes. > > It's not clear from the web site in question that the relevant code is > released under the PostgreSQL license. git clone

Re: [HACKERS] CTE inlining

On Mon, May 1, 2017 at 7:22 AM, Pavel Stehule wrote: > > > 2017-05-01 1:21 GMT+02:00 Andres Freund : >> >> On 2017-04-30 07:19:21 +0200, Pavel Stehule wrote: >> > why we cannot to introduce GUC option - enable_cteoptfence ? >> >> Doesn't really solve the issue, and we've generally shied away from

Re: [HACKERS] SQL/JSON in PostgreSQL

On Fri, Sep 15, 2017 at 7:31 PM, Robert Haas wrote: > On Fri, Sep 15, 2017 at 10:10 AM, Daniel Gustafsson wrote: >> Can we expect a rebased version of this patch for this commitfest? Since >> it’s >> a rather large feature it would be good to get it in as early as we can in >> the >> process.

Re: [HACKERS] SQL/JSON in PostgreSQL

On 16 Sep 2017 02:32, "Nikita Glukhov" wrote: On 15.09.2017 22:36, Oleg Bartunov wrote: On Fri, Sep 15, 2017 at 7:31 PM, Robert Haas wrote: > >> On Fri, Sep 15, 2017 at 10:10 AM, Daniel Gustafsson >> wrote: >> >>> Can we expect a rebased version of t

Re: [HACKERS] Add Roman numeral conversion to to_number

On 3 Aug 2017 16:29, "Oliver Ford" wrote: Adds to the to_number() function the ability to convert Roman numerals to a number. This feature is on the formatting.c TODO list. It is not currently implemented in either Oracle, MSSQL or MySQL so gives PostgreSQL an edge :-) I see use of this in full

Re: [HACKERS] [PATCH] Generic type subscripting

On Fri, Sep 22, 2017 at 3:51 PM, Peter Eisentraut wrote: > On 9/21/17 11:24, Dmitry Dolgov wrote: >> One last thing that I need to clarify. Initially there was an idea to >> minimize changes in `pg_type` > > I see, but there is no value in that if it makes everything else more > complicated. +1

Re: [HACKERS] Surjective functional indexes

On Thu, May 25, 2017 at 7:30 PM, Konstantin Knizhnik wrote: > Right now Postgres determines whether update operation touch index or not > based only on set of the affected columns. > But in case of functional indexes such policy quite frequently leads to > unnecessary index updates. > For example,

Re: [HACKERS] Speakers Wanted for pgDay Cuba

I'm probably going, but my company supports this trip. On Thu, Jul 23, 2015 at 10:35 PM, Josh Berkus wrote: > Contributors: > > We are looking for one or more PostgreSQL contributors to travel to > Havana, Cuba, to present at the second pgDay Cuba. In order to > encourage this young community,

Re: [HACKERS] "A huge debt of gratitude" - Michael Stonebraker

Nice to hear you again Jolly ! On Wed, Jul 22, 2015 at 1:42 AM, Jolly Chen wrote: > Hey everyone, > > You have probably heard that Mike Stonebraker recently won the Turing > award. A recording of his award lecture is available at: > https://www.youtube.com/watch?v=BbGeKi6T6QI > > It is an enter

Re: [HACKERS] GIN pending list clean up exposure to SQL

On Thu, Aug 13, 2015 at 2:19 AM, Jeff Janes wrote: > I've written a function which allows users to clean up the pending list. > It takes the index name and returns the number of pending list pages > deleted. > > # select * from gin_clean_pending_list('foo_text_array_idx'); > gin_clean_pending_li

Re: [HACKERS] jsonb array-style subscripting

On Mon, Aug 17, 2015 at 11:26 PM, Peter Geoghegan wrote: > On Mon, Aug 17, 2015 at 12:26 PM, Merlin Moncure > wrote: > > ...is a good idea. postgres operators tend to return immutable copies > > of the item they are referring to. > > This patch does not add an operator at all, actually. If feels

Re: [HACKERS] Proposal: Implement failover on libpq connect level.

On Wed, Aug 19, 2015 at 4:46 PM, Andres Freund wrote: > On 2015-08-19 09:41:32 -0400, Tom Lane wrote: > > In fact, they'd still need to use DNS balancing for Postgres, > > because not everything connects with libpq (think JDBC for instance). > > It already does support this though. > > https://jd

Re: [HACKERS] Horizontal scalability/sharding

>> accepted. >> >> June, 2015: I attended the PGCon sharding unconference session and >> there was a huge discussion about where we should go with sharding. >> I think the big take-away was that most people liked the FDW approach, >> but had business/customer

Re: [HACKERS] Horizontal scalability/sharding

On Mon, Aug 31, 2015 at 5:48 AM, Bruce Momjian wrote: > On Sun, Aug 30, 2015 at 10:08:06PM -0400, Bruce Momjian wrote: > > On Mon, Aug 31, 2015 at 09:53:57AM +0900, Michael Paquier wrote: > > > Well, I have had many such discussions with XC/XL folks, and that > was my > > > opinion. I ha

Re: [HACKERS] Horizontal scalability/sharding

On Tue, Sep 1, 2015 at 7:08 PM, Robert Haas wrote: > On Tue, Sep 1, 2015 at 12:00 AM, Pavan Deolasee > wrote: > > My worry is that if we start implementing them again from scratch, it > will > > take a few years before we get them in a usable state. What XC/XL lacked > is > > probably a Robert H

[HACKERS] Fwd: [Snowball-discuss] New website

Snowball stemmer has moved to the new site http://snowballstem.org, I made a simple patch for master . I'm not sure if it's ok for 9.5. -- Forwarded message -- From: Olly Betts Date: Mon, Sep 7, 2015 at 1:46 AM Subject: [Snowball-discuss] New website To: snowball-disc...@lists.ta

Re: [HACKERS] nested hstore patch

Erik, thanks for docs fixes, we have even more :) Oleg On Tue, Jan 14, 2014 at 4:18 AM, Erik Rijkers wrote: > On Mon, January 13, 2014 18:30, Andrew Dunstan wrote: >> >> >> On 01/13/2014 11:16 AM, Oleg Bartunov wrote: >>> Andrew, >>> >>> d

Re: [HACKERS] nested hstore patch - FailedAssertion("!(value->array.nelems == 1)

It doesn't crashed in the last version in our repository. =# select 'x'::hstore || ('a=>"1"':: hstore) ; ?column? --- "x", "a", "1" (1 row) On Wed, Jan 15, 2014 at 3:53 AM, Erik Rijkers wrote: > On Mon, January 13, 2014 16:36, Andrew Dunstan wrote: >> A new version of the patc

Re: [HACKERS] nested hstore patch - FailedAssertion("!(value->array.nelems == 1)

https://github.com/feodor/postgres On Wed, Jan 15, 2014 at 11:10 AM, Erik Rijkers wrote: > On Wed, January 15, 2014 08:01, Oleg Bartunov wrote: >> It doesn't crashed in the last version in our repository. >> >> =# select 'x'::hstore ||

Re: [HACKERS] jsonb and nested hstore

Hmm, neither me, nor Teodor have experience and knowledge with populate_record() and moreover hstore here is virgin and we don't know the right behaviour, so I think we better take it from jsonb, once Andrew realize it. Andrew ? On Fri, Jan 31, 2014 at 4:52 AM, Andrew Dunstan wrote: > > On 01/30/

Re: [HACKERS] GIN improvements part2: fast scan

Tomasa, it'd be nice if you use real data in your testing. One very good application of gin fast-scan is dramatic performance improvement of hstore/jsonb @> operator, see slides 57, 58 http://www.sai.msu.su/~megera/postgres/talks/hstore-dublin-2013.pdf. I'd like not to lost this benefit :) Oleg

Re: [HACKERS] jsonb and nested hstore

Andrew provided us more information and we'll work on recv. What people think about testing this stuff ? btw, we don't have any regression test on this. Oleg On Wed, Feb 5, 2014 at 2:03 AM, Josh Berkus wrote: > On 02/03/2014 07:27 AM, Andres Freund wrote: >> On 2014-02-03 09:22:52 -0600, Merlin

Re: [HACKERS] jsonb and nested hstore

Yes, the repository you mentioned is the last version of our development. It contains various fixes of issues by Andres, but we are waiting Andrew, who is working on jsonb stuff. On Mon, Feb 24, 2014 at 5:34 PM, Tomas Vondra wrote: > On 7.2.2014 00:47, Andrew Dunstan wrote: >> >> On 02/05/2014 10

Re: [HACKERS] jsonb and nested hstore

Andres, you can always look at our development repository: https://github.com/feodor/postgres/tree/hstore - hstore only, https://github.com/feodor/postgres/tree/jsonb_and_hstore - hstore with jsonb Since we were concentrated on the jsonb_and_hstore branch we usually wait Andrew, who publish patch

Re: [HACKERS] jsonb and nested hstore

On Mon, Mar 3, 2014 at 7:22 PM, Andres Freund wrote: > Hi Oleg, > > On 2014-03-03 19:17:12 +0400, Oleg Bartunov wrote: >> Since we were concentrated on the jsonb_and_hstore branch we usually >> wait Andrew, who publish patch. You last issues were addressed in >> bot

Re: [HACKERS] jsonb and nested hstore

Thanks, looks like a bug. On Tue, Mar 4, 2014 at 12:38 PM, Peter Geoghegan wrote: > Hi Oleg, > > On Mon, Mar 3, 2014 at 7:17 AM, Oleg Bartunov wrote: >> you can always look at our development repository: > > I think I found a bug: > > [local]/postgres=# \d+ bar >

Re: [HACKERS] jsonb and nested hstore

I tried try.mongodb.com > 25 == 25.0 true On Tue, Mar 4, 2014 at 2:18 PM, Peter Geoghegan wrote: > On Tue, Mar 4, 2014 at 2:18 AM, Teodor Sigaev wrote: >> That is because compareJsonbValue compares numeric values with a help of >> numeric_cmp() instead of comparing text representation. This inc

Re: [HACKERS] jsonb and nested hstore

On Thu, Mar 6, 2014 at 12:43 PM, Peter Geoghegan wrote: > On Thu, Mar 6, 2014 at 12:23 AM, Teodor Sigaev wrote: >> That's possible to introduce GUC variable for i/o functions which will >> control old "bug-to-bug" behavior. IMHO, this is much better option that >> stopping hstore development or s

Re: [HACKERS] jsonb and nested hstore

Hi there, Looks like consensus is done. I and Teodor are not happy with it, but what we can do :) One thing I want to do is to reserve our contribution to the flagship feature (jsonb), particularly, "binary storage for nested structures and indexing. Their work was sponsored by Engine Yard". A

Re: [HACKERS] jsonb and nested hstore

I meant in Release Notes for 9.4 On Thu, Mar 6, 2014 at 10:26 PM, Andrew Dunstan wrote: > > > > > > On 03/06/2014 12:50 PM, Oleg Bartunov wrote: >> >> Hi there, >> >> Looks like consensus is done. I and Teodor are not happy with it, but >> w

Re: [HACKERS] jsonb and nested hstore

On Thu, Mar 6, 2014 at 10:54 PM, Josh Berkus wrote: g? > > On 03/06/2014 09:50 AM, Oleg Bartunov wrote:> Looks like consensus is > done. I and Teodor are not happy with it, but >> what we can do :) One thing I want to do is to reserve our >> contribution to the

Re: [HACKERS] Hstore: Query speedups with Gin index

Michael, take a look on http://obartunov.livejournal.com/171959.html As for the indexing stuff we already thought many times about key&value mixing, but real solution, probably, could come from spgist and gin combination. I mean, spgist (suffix array) instead of btree for avoiding key duplication

Re: [HACKERS] [v9.4] row level security

btw, there is serious problem with row-level security and constraints. For example, user with low security level could use unique constraint to know about existence of a row with higher security. I don't know, what is the best practice to avoid this. On Wed, Aug 28, 2013 at 1:37 AM, Greg Smith

Re: [HACKERS] [v9.4] row level security

Any constraints could be "covert channel". On Wed, Aug 28, 2013 at 4:17 PM, Kohei KaiGai wrote: > 2013/8/28 Oleg Bartunov : > > btw, there is serious problem with row-level security and constraints. > For > > example, user with low security level could use unique

Re: [HACKERS] Hstore: Query speedups with Gin index

Blake, I think it's better to implement this patch as a separate opclass, so users will have option to choose indexing. Oleg On Tue, Sep 3, 2013 at 6:24 PM, Blake Smith wrote: > Thanks for the feedback everyone. I've attached the patch that we are now > running in production to service our hs

Re: [HACKERS] Hstore: Query speedups with Gin index

assing for me locally with the --enable-cassert configure flag. Please let > me know what you think and if there is any other work that would need to be > done (style cleanups, updating documentation, etc) to get this merged. > > Thanks! > > Blake > > > > > &g

[HACKERS] \h open

I noticed there is nothing available in built-in psql help about OPEN command. Does it intentional ? postgres=# \h open No help available for "open". Try \h with no arguments to see available help. Oleg

Re: [HACKERS] Looking for information on our elephant

Tatsuo, I have emails even from 1995 ! You can see that historical message here: http://www.pgsql.ru/db/mw/msg.html?mid=1238939 Re: [HACKERS] PostgreSQL logo. *Author:* yang( at )sjuphil( dot )sju( dot )edu *Date:* 1997-04-03 20:36:33 *Subject:*

Re: [HACKERS] Looking for information on our elephant

Tatsuo, you could ask Marc about archives. Probably he has original mbox files. Oleg On Sun, Sep 22, 2013 at 11:18 AM, Tatsuo Ishii wrote: > Oleg, > > Unfortunately the archives seem to miss attached files. I love to see > the attached files because they are logo images. Any idea? > -- > Tat

  1   2   3   4   5   6   7   8   9   10   >