Greetings,
* Joshua D. Drake (j...@commandprompt.com) wrote:
> I don't recall, do we allow non-bug fix (or what constitutes a bug)
> for back branches with docs? I have been reviewing the logical
> replication docs and they could use some love but I need to know
> which branch I should start work

Tom, Robert, all,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Robert Haas writes:
> > OK, let me try to summarize where we are with this.
>
> > Currently, postgres_fdw requires a password unless you are logged in
> > as a superuser. Jeff proposes to change that so that it

Tom,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Stephen Frost <sfr...@snowman.net> writes:
> > Isn't the first concern addressed by using SPI..?
>
> I did not look at the patch yet, but TBH if it uses SPI for sub-operations
> of ALTER TABLE I think that is sufficient

Robert, all,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Fri, Dec 1, 2017 at 12:31 AM, Michael Paquier
> wrote:
> > I am moving this patch to next CF 2018-01.
>
> There now seems to be a consensus for superuser -> superuser_arg
> rather than what Jeff did

Bruce,
* Bruce Momjian (br...@momjian.us) wrote:
> On Tue, Dec 5, 2017 at 09:16:02AM -0500, Stephen Frost wrote:
> > > There are clusters that take a long time to dump the schema from the old
> > > cluster and recreate it in the new cluster. One idea of speeding up
&

Bruce,
* Bruce Momjian (br...@momjian.us) wrote:
> > In any case, of course, if we're able to move part of what pg_upgrade
> > does to be while the old server is online then that takes whatever the
> > cost of that is out of the downtime window. The question is if that's a
> > 5% improvement in

Greetings -hackers,
Google Summer of Code 2018 was announced back in September and they've
changed up the timeline a bit [1]. Specifically, they moved up the
dates for things like the mentoring organization application deadline,
so it's time to start working on our Idea's page for 2018 in

Aleksander,
* Aleksander Alekseev (a.aleks...@postgrespro.ru) wrote:
> > HA/fail-over is a very broad topic, with a lot of pieces that need to be
> > done such that I'm not sure it's really viable, but perhaps a precursor
> > project (synchronous logical replication seems like a prereq, no?)

Aleksander,
* Aleksander Alekseev (a.aleks...@postgrespro.ru) wrote:
> > New entries are certainly welcome and encouraged, just be sure to note
> > them as '2018' when you add it.
>
> I proposed a few ideas:
Thanks!
> * High availability / failover based on logical replication
> * Thrift

Alex,
* Alex Kliukin (al...@hintbits.com) wrote:
> On Fri, Dec 15, 2017, at 14:52, Aleksander Alekseev wrote:
> > Completely agree, this project can be an improvement for Stolon (or
> > Patroni, but I personally never tested or used it, also I got a feeling
> > that Google guys will prefer a

Andres,
* Andres Freund (and...@anarazel.de) wrote:
> On 2017-12-12 18:04:44 -0500, David Steele wrote:
> > If the forks are written out of order (i.e. main before init), which is
> > definitely possible, then I think worst case is some files will be backed up
> > that don't need to be. The main

Magnus, all,
* Magnus Hagander (mag...@hagander.net) wrote:
> mbox access should now be restored, and as Stephen says, now handled by the
> Date in the message. Let me know if there are any issues with the new ones.
> (They're now generated by the same code as the per-thread ones).
And just fyi,

Greetings,
* Tatsuo Ishii (is...@sraoss.co.jp) wrote:
> > This list has now been migrated to new mailing list software known as
> > 'PGLister'. This migration will impact all users of this mailing list
> > in one way or another.
> >
> > If you would like to unsubscribe from this mailing list,

Greetings!
This list has now been migrated to new mailing list software known as
'PGLister'. This migration will impact all users of this mailing list
in one way or another.
If you would like to unsubscribe from this mailing list, please click on
'Show Original' or 'Show Headers' in your client

Greeting, Sophie!
* Sophie Herold (sophi...@hemio.de) wrote:
> I did not find any advice on how to choose a new OID for pg_proc.
(Haven't looked at the patch itself yet really, but wanted to answer
this.)
The main thing is to not duplicate the OID, which you can avoid by
calling 'unused_oids'

Bruce,
* Bruce Momjian (br...@momjian.us) wrote:
> I think the big problem with two-stage pg_upgrade is that the user steps
> are more complex, so what percentage of users are going use the
> two-stage method. The bad news is that only a small percentage of users
> who will benefit from it will

Mark,
* Mark Dilger (hornschnor...@gmail.com) wrote:
> > On Dec 7, 2017, at 10:24 PM, Bruce Momjian wrote:
> > I think the big problem with two-stage pg_upgrade is that the user steps
> > are more complex, so what percentage of users are going use the
> > two-stage method. The

Alexander,
* Alexander Kukushkin (cyberd...@gmail.com) wrote:
> Couple of months ago we at Zalando upgraded a few databases of different
> sizes to 9.6.
Thanks for sharing your experience!
> During preparations to the I've found 2.5 pain-points:
>
> 1. We are using schema-based api deployment.

Tom,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Stephen Frost <sfr...@snowman.net> writes:
> > If we go down that route, since this makes a pretty serious difference
> > in terms of what the user has to deal with post-pg_upgrade, I'd suggest
> > we require an additional

Bruce,
* Bruce Momjian (br...@momjian.us) wrote:
> As part of PGConf.Asia 2017 in Tokyo, we had an unconference topic about
> zero-downtime upgrades. After the usual discussion of using logical
> replication, Slony, and perhaps having the server be able to read old
> and new system catalogs, we

Greetings,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Andrew Dunstan writes:
> > On 05/06/2018 11:53 AM, Tom Lane wrote:
> >> What sort of changes do we get if we remove those two flags as you prefer?
> >> It'd help to see some examples.
>
> > Essentially it adds

Greetings,
* Aleksander Alekseev (a.aleks...@postgrespro.ru) wrote:
> > I understand that you're open to having it as a new data type or as a
> > bytea, but I don't agree. This should be a new data type, just as json
> > is a distinct data type and so is jsonb.
>
> Could you please explain in a

Michael,
* Michael Paquier (mich...@paquier.xyz) wrote:
> On Sun, May 06, 2018 at 01:46:28PM -0400, Stephen Frost wrote:
> > I definitely prefer to have the braces on their own line- makes working
> > with the files a lot easier when you've got a lot of hashes
> > (partic

Greetings,
* Peter Geoghegan (p...@bowt.ie) wrote:
> On Thu, Apr 26, 2018 at 10:39 AM, Robert Haas wrote:
> > I'm personally not very excited about making rules like "index pages
> > are more valuable than heap pages". Such rules will in many cases be
> > true, but it's

Greetings,
* Michael Paquier (mich...@paquier.xyz) wrote:
> There is dory in the buildfarm which compiles using VS 2015, but it runs
> only 9.6 and newer versions.
That would be specifically because compiling 9.5 didn't work.. We'd be
happy to have dory running on older major versions, if

Greetings,
* Michael Paquier (mich...@paquier.xyz) wrote:
> On Sun, May 06, 2018 at 09:14:06PM -0400, Stephen Frost wrote:
> > While I appreciate the support, I'm not sure that you're actually
> > agreeing with me.. I was arguing that braces should be on their own
> &g

Greetings,
* Aleksander Alekseev (a.aleks...@postgrespro.ru) wrote:
> >> Personally I think raw data bytes are OK if functions for getting all
> >> keys and values from this data are provided
> >
> > What is the purpose of using Thrift "encoding" if it turns out to be a
> > simple wrapper for

Greetings,
* Peter Geoghegan (p...@bowt.ie) wrote:
> Whether or not Andrew's patch is formally classified as a bug fix is
> subjective. I'm inclined to accept it as a bug fix, but I also think
> that it shouldn't matter very much. The practical implication is that
> I don't think it's completely

Greetings,
* Carter Thaxton (carter.thax...@gmail.com) wrote:
> Many times I've wanted to export a subset of a database, using some sort of
> row filter condition on some of the large tables. E.g. copying a
> production database to a staging environment, but with some time series
> data only

Greetings Robbie!
* Robbie Harwood (rharw...@redhat.com) wrote:
> Zombie patch is back from the dead. It's been a bit more than two years
> since v12 (the last major revision) and almost three since it was
> originally submitted. (I do have enough pride to point out that it did
> not actually

Greetings,
* Abhijit Menon-Sen (a...@2ndquadrant.com) wrote:
> At 2018-05-18 20:27:57 -0400, sfr...@snowman.net wrote:
> >
> > I don't agree with the general notion that we can't have a function
> > which handles the complicated bits about the kind of error because
> > someone grep'ing the source

Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Tue, May 15, 2018 at 6:07 PM, Tom Lane wrote:
> > That seems like an awful lot of work to handle what's still going to be
> > a pretty small set of permissions. Every permission we add is going to
> > have to be

Greetings,
* Andrew Dunstan (andrew.duns...@2ndquadrant.com) wrote:
> Well, this went quiet. I'm happy to be CFM and assisted by Michael and
> Ashutosh
>
> Are there any privileges required that I should see about obtaining?
I've set you up with the cf admin privs (which Michael also has).

Greetings,
* Konstantin Knizhnik (k.knizh...@postgrespro.ru) wrote:
> There was very interesting presentation at pgconf about pg_prefaulter:
>
> http://www.pgcon.org/2018/schedule/events/1204.en.html
I agree and I've chatted a bit w/ Sean further about it.
> But it is implemented in GO and

Greetings,
* Magnus Hagander (mag...@hagander.net) wrote:
> On Tue, Jun 5, 2018 at 4:45 PM, Chris Travers
> wrote:
> > If I may suggest: The committee should be international as well and
> > include people from around the world. The last thing we want is for it to
> > be dominated by people

would prefer it be directly visible with the connection itself. With
> some guidance from Stephen Frost I've put together this patch which does
> that.
Yeah, I tend to agree that it'd be extremely useful to have this
included in the 'connection authorized' message.
> It adds a new a

Greetings,
* Peter Geoghegan (p...@bowt.ie) wrote:
> FWIW, I developed a document on committing for my own reference, with
> some help from Andres. A lot of it is about commit message style, the
> use of fields, and so on. But I've also developed a check list for
> committing, knowing that there

Greetings,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> [ Thanks to Stephen for cranking up a continuous build loop on dory ]
That was actually Heath, who is also trying to work this issue and has
an idea about something else which might help (and some more information
about what's happening in the

Greetings,
* Heath Lord (heath.l...@crunchydata.com) wrote:
>Any ideas or changes that we could do to help debug or verify would be
> helpful. We have considered changing it to run everything as SYSTEM but if
> possible we would like to avoid this for security reasons. Thank you in
>

Robert, all,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Tue, Nov 21, 2017 at 9:26 AM, Amit Kapila wrote:
> > +1. I was also once confused with these macros. I think this is a
> > good cleanup. On a quick look, I don't see any problem with your
> > changes.
>
>

Greetings,
* Michael Paquier (michael.paqu...@gmail.com) wrote:
> On Thu, Nov 9, 2017 at 12:33 PM, Ashutosh Bapat
> wrote:
> > Looking at order_qual_clauses(), we can say that a set of quals q1
> > qn are ordered the same irrespective of the set of clauses

Doug,
* Rady, Doug (radyd...@amazon.com) wrote:
> This patch enables building pgbench to use ppoll() instead of select()
> to allow for more than (FD_SETSIZE - 10) connections. As implemented,
> when using ppoll(), the only connection limitation is system resources.
Looks like this patch had

Greetings Ryan!
* Ryan Murphy (ryanfmur...@gmail.com) wrote:
> Stephen, so far I've read thru your patch and familiarized myself with some
> of the auth functionality in pg_authid.h and src/backend/utils/adt/acl.c
>
> The only question I have so far about your patch is the last several hunks of

Greetings Ildar,
* Fabien COELHO (coe...@cri.ensmp.fr) wrote:
> >>I noticed from the source of all human knowledege (aka Wikipedia:-)
> >>that there seems to be a murmur3 successor. Have you considered it?
> >>One good reason to skip it would be that the implementation is long
> >>and complex.

Geoff, all,
* Geoff Winkless (pgsqlad...@geoff.dj) wrote:
> On 15 January 2018 at 16:10, Robert Haas wrote:
> >
> > More broadly, I think what is needed here is less C-fu than
> > English-fu. If we come up with something good, we can make it print
> > that thing.
>
> Can

Greetings!
I've gone through and cleaned up our GSoC 2018 Wiki page:
https://wiki.postgresql.org/wiki/GSoC_2018
Please review! If you have any last-minute items, please add them!
We could use some more mentors! If you would have some time over the
summer to help with mentoring a GSoC project

Michael, all,
* Michael Paquier (michael.paqu...@gmail.com) wrote:
> On Thu, Jan 18, 2018 at 02:04:45PM +, Ryan Murphy wrote:
> > I had not tried this before with my unpatched build of postgres. (In
> > retrospect of course I should have). I expected my superuser to be
> > able to perform

Chris,
* Chris Travers (chris.trav...@adjust.com) wrote:
> Attached is the patch as submitted for commitfest.
This has been stuck in Waiting for Author since before the commitfest
started. I'll try to kick-start it but it seems like it's stuck because
there's a fundamental disagreement about if

Tom,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> > On Monday, January 22, 2018, Stephen Frost <sfr...@snowman.net> wrote:
> >> In the end, I feel like this patch has actually been through the ringer
> >> and back because it was brought up in the context of solving a p