Greetings,
On Tue, Nov 16, 2021 at 13:16 Alvaro Herrera
wrote:
> On 2021-Nov-16, Stephen Frost wrote:
>
> > Not against possibly changing that but I don’t get the point of including
> > be-gssapi-common.h if it’s not enabled in the build and typically if
> GSSAPI
> >
Greetings,
On Tue, Nov 16, 2021 at 15:12 Tom Lane wrote:
> Alvaro Herrera writes:
> > On 2021-Nov-16, Stephen Frost wrote:
> >> Not against possibly changing that but I don’t get the point of
> including
> >> be-gssapi-common.h if it’s not enabled in the build and
Greetings,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Michael Paquier writes:
> > On Thu, Nov 25, 2021 at 06:19:03PM -0800, SATYANARAYANA NARLAPURAM wrote:
> >> If we are keeping it then why not make it better?
>
> > Well, non-exclusive backups are better by design in many aspects, so I
> > don't
Greetings,
On Tue, Nov 30, 2021 at 11:47 Laurenz Albe wrote:
> On Tue, 2021-11-30 at 09:20 -0500, Stephen Frost wrote:
> > Greetings,
> >
> > * Tom Lane (t...@sss.pgh.pa.us) wrote:
> > > Michael Paquier writes:
> > > > On Thu, Nov 25, 2021 at 06:19:03
Greetings,
* Michael Paquier (mich...@paquier.xyz) wrote:
> On Fri, Mar 23, 2018 at 01:38:38AM +0900, Fujii Masao wrote:
> > Personally it looks very intrusive, so I'm feeling inclined to push
> > the changes without that refactoring.
I've been reading over the first couple of posted patches and
Greetings,
* Michael Paquier (mich...@paquier.xyz) wrote:
> On Sat, Mar 24, 2018 at 11:14:34PM -0400, Tom Lane wrote:
> > Stephen Frost writes:
> >> I don't completely buy off on the argument that having these #define's
> >> would make it easier for forks
the .so changed, but the existing functions are still in
place with their current public-execute rights.
Thanks!
Stephen
From 296b407863a7259a04e5e8cfc19f9b8ea124777c Mon Sep 17 00:00:00 2001
From: Stephen Frost
Date: Wed, 7 Mar 2018 06:42:42 -0500
Subject: [PATCH 1/2] Remove explicit superuser ch
Greetings,
* David Rowley (david.row...@2ndquadrant.com) wrote:
> On 16 March 2018 at 13:46, Tomas Vondra wrote:
> > I've done more testing on this patch, and I haven't found any new issues
> > with it, so PFA I'm marking it as ready for committer.
>
> Great! Many thanks for the review.
I read
Greetings,
* Chapman Flack (c...@anastigmatix.net) wrote:
> On 03/18/18 19:28, Daniel Gustafsson wrote:
> > It seems expensive to regex over BLCKSZ, but it’s probably the safest option
> > and it’s not a performance critical codepath. Feel free to whack the test
> > patch over the head with the a
Greetings,
* David Rowley (david.row...@2ndquadrant.com) wrote:
> On 26 March 2018 at 15:26, Stephen Frost wrote:
> > The header at the top of datumCopy() pretty clearly says that it's for
> > "non-NULL" datums, yet this function seems to be happily ignoring that
&g
Greetings,
* Teodor Sigaev (teo...@sigaev.ru) wrote:
> Will autovacuum (or something else) complain about absense of relfile during
> orphan table deleting? I mean, you get a base backup without temp tables,
> then you try to run postgres on it and will it complain about existing
> record in pg_cl
Greetings,
* Tomas Vondra (tomas.von...@2ndquadrant.com) wrote:
> On 03/26/2018 10:27 PM, Tom Lane wrote:
> > I fear that what will happen, if we commit this, is that something like
> > 0.01% of the users of array_agg and string_agg will be pleased, another
> > maybe 20% will be unaffected because
Greetings,
* Craig Ringer (cr...@2ndquadrant.com) wrote:
> On 26 March 2018 at 21:05, Damir Simunic
> wrote:
> > The same goes for the ‘authorization’ header. Postgres does not support
> > Bearer token authorization today. But maybe you’ll be able to define a
> > function that knows how to deal w
Greetings Tom, all,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Alvaro Herrera writes:
> > Simon Riggs wrote:
> >> JIT means Just In Time, which could be applied to many concepts and
> >> has been in use for many years in a range of concepts. particularly in
> >> manufacturing/logistics and project
Greetings,
* Andres Freund (and...@anarazel.de) wrote:
> On 2018-03-29 13:26:31 -0400, Robert Haas wrote:
> > On Thu, Mar 29, 2018 at 9:44 AM, Tom Lane wrote:
> > > I'd go a little further and drop "JIT" from user-facing documentation
> > > altogether. Instead refer to the feature as "compilatio
Greetings,
* Magnus Hagander (mag...@hagander.net) wrote:
> On Fri, Mar 30, 2018 at 5:35 AM, David Steele wrote:
>
> > On 3/24/18 10:32 AM, Michael Banck wrote:
> > > Am Freitag, den 23.03.2018, 17:43 +0100 schrieb Michael Banck:
> > >> Am Freitag, den 23.03.2018, 10:54 -0400 schrieb David Steel
Greetings,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Chapman Flack writes:
> > On 03/27/18 22:10, Michael Paquier wrote:
> >> Here you go for one example:
> >> https://sourceforge.net/projects/pglesslog/
>
> > In any case, from my study of the commit, it is hard for me to see an issue.
> > The co
Greetings,
* Michael Paquier (mich...@paquier.xyz) wrote:
> On Sun, Mar 25, 2018 at 09:43:25PM -0400, Stephen Frost wrote:
> > * Michael Paquier (mich...@paquier.xyz) wrote:
> >> On Thu, Mar 08, 2018 at 10:15:11AM +0900, Michael Paquier wrote:
> >> > Other than that
Greetings,
* Anthony Iliopoulos (ail...@altatus.com) wrote:
> On Mon, Apr 02, 2018 at 12:32:45PM -0700, Andres Freund wrote:
> > On 2018-04-02 20:53:20 +0200, Anthony Iliopoulos wrote:
> > > On Mon, Apr 02, 2018 at 11:13:46AM -0700, Andres Freund wrote:
> > > > Throwing away the dirty pages *and*
Greetings,
* Andres Freund (and...@anarazel.de) wrote:
> i.e. memory consumption differs between environments. Which isn't
> surprising.
>
> I wonder if we could disable the display with a separate switch or tie
> it to !'COSTS OFF && TIMING OFF' or such?
Yeah, I agree with having these suppress
Michael, all,
* Michael Paquier (mich...@paquier.xyz) wrote:
> On Sun, Apr 01, 2018 at 09:39:02AM -0400, Stephen Frost wrote:
> > Thanks for checking. Attached is an updated version which also includes
> > the changes for adminpack, done in a similar manner to how pgstattuple
>
Michael,
* Michael Paquier (mich...@paquier.xyz) wrote:
> On Mon, Apr 02, 2018 at 05:09:21PM -0400, Stephen Frost wrote:
> > * Michael Paquier (mich...@paquier.xyz) wrote:
> >> No refactoring for pg_file_unlink and its v1.1?
> >
> > I considered each function and th
Greetings,
* Andres Freund (and...@anarazel.de) wrote:
> On 2018-04-05 14:39:27 -0400, Tom Lane wrote:
> > Andres Freund writes:
> > > ISTM the better approach would be to try to reduce the cost of
> > > PostmasterIsAlive() on common platforms - it should be nearly free if
> > > done right.
> >
Greetings,
* Michael Paquier (mich...@paquier.xyz) wrote:
> On Thu, Apr 05, 2018 at 12:08:15PM -0400, David Steele wrote:
> > On 4/5/18 2:55 AM, Michael Paquier wrote:
> >> On Wed, Apr 04, 2018 at 08:03:54PM -0400, David Steele wrote:
> >>
> >>> Instead I have created variables in file_perm.c
> >
David,
* David Steele (da...@pgmasters.net) wrote:
> The GUC shows the current mode of the data directory, while the
> variables in file_perm.c store the mode that should be used to create
> new dirs/files. One is certainly based on the other but I thought it
> best to split them for clarity.
Ag
Michael,
* Michael Paquier (mich...@paquier.xyz) wrote:
> On Fri, Apr 06, 2018 at 09:15:15AM -0400, Stephen Frost wrote:
> > I'll reply to David's last email (where the latest set of patches were
> > included) with my comments/suggestions and I expect we'll be a
Greetings,
* Heikki Linnakangas (hlinn...@iki.fi) wrote:
> On 06/04/18 19:39, Andres Freund wrote:
> >On 2018-04-06 07:39:28 -0400, Stephen Frost wrote:
> >>While I tend to agree that it'd be nice to just make it cheaper, that
> >>doesn't seem like something
Greetings,
* Stephen Frost (sfr...@snowman.net) wrote:
> Great, thanks. I'll be doing more review of it myself and see about
> pushing it later this afternoon.
Took a bit longer as I wanted to check over a few more things, but I've
now pushed this. Thanks much for all of the
Greetings Fabien,
* Fabien COELHO (fabien.coe...@mines-paristech.fr) wrote:
> >>Here is a v14, after yet another rebase, and some comments added to
> >>answer your new comments.
> >
> >Attached v15 is a simple rebase after Teodor push of new functions &
> >operators in pgbench.
>
> Patch v16 is a
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Fri, Apr 6, 2018 at 6:56 PM, Andres Freund wrote:
> > no one can entirely quibble with the rationale that this is ok (I'll
> > post a patch cleaning up the atomics simulation of flags in a bit), but
> > this is certainly not a correct l
Andres,
* Andres Freund (and...@anarazel.de) wrote:
> On 2018-04-06 19:31:56 -0400, Stephen Frost wrote:
> > I'm quite sure that bringing up MERGE in this thread and saying it needs
> > to be reverted without even having the committer of that feature on the
> > CC list
David,
* David Steele (da...@pgmasters.net) wrote:
> On 4/6/18 6:04 PM, David Steele wrote:
> >On 4/6/18 3:02 PM, Stephen Frost wrote:
> >>
> >>- Further discussion in the commit messages
> >
> >Agreed, these need some more work. I'm happy to do th
Fabien,
* Fabien COELHO (fabien.coe...@mines-paristech.fr) wrote:
> Patch v16 is a rebase.
Here's that review.
> diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml
> index d52d324..203b6bc 100644
> --- a/doc/src/sgml/ref/pgbench.sgml
> +++ b/doc/src/sgml/ref/pgbench.sgml
David,
* David Steele (da...@pgmasters.net) wrote:
> On 4/6/18 10:22 PM, Stephen Frost wrote:
> > * David Steele (da...@pgmasters.net) wrote:
> >> On 4/6/18 6:04 PM, David Steele wrote:
> >>> On 4/6/18 3:02 PM, Stephen Frost wrote:
> >>>>
>
Tom,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Stephen Frost writes:
> > Time to watch the buildfarm,
>
> That didn't take long.
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2018-04-07%2021%3A50%3A02
Yes, I'm taking a look at it
Greetings,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Stephen Frost writes:
> > * Tom Lane (t...@sss.pgh.pa.us) wrote:
> >> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2018-04-07%2021%3A50%3A02
>
> > Yes, I'm taking a look at it.
>
Greetings,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> (If not, this bodes ill for the Windows results.)
Ah, there go the Windows builds... Missing a #else clause where we
should have one for those systems, will fix.
Thanks!
Stephen
signature.asc
Description: PGP signature
Fabien,
* Fabien COELHO (coe...@cri.ensmp.fr) wrote:
> >>
> >>+
> >>+
> >>+ \cset [prefix] or
> >>+ \gset [prefix]
> >>+
> >
> >Seems like this should really be moved down below the section for
> >'\set'.
>
> Dunno.
>
> I put them there because it is in alphabetical order (
Greetings,
* Peter Eisentraut (peter.eisentr...@2ndquadrant.com) wrote:
> On 4/5/18 02:04, Pavel Raiskup wrote:
> > Hello, for the support of multiple versions of PostgreSQL RPM packages on
> > one system, we are thinking about having only one libpq.so.5
> > (libecpg.so.6, libpgtype.so.3 respectiv
Greetings,
* Andres Freund (and...@anarazel.de) wrote:
> On 2018-04-18 06:36:38 -0400, Heikki Linnakangas wrote:
> > On 18/04/18 06:10, Konstantin Knizhnik wrote:
> > > But there are still use cases which can not be covered y external
> > > connection pooler.
> >
> > Can you name some? I understa
Greetings,
* Andres Freund (and...@anarazel.de) wrote:
> It's common that half the buildfarm has reported back before a single
> windows buildfarm animal reports. And if they report a failure one often
> has to wait for hours for the next run.
Yes, that's been rather annoying.
> It'd be awesome
Greetings,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> So far, dory has failed three times with essentially identical symptoms:
>
> 2018-04-23 19:57:10.624 GMT [2240] FATAL: could not reattach to shared
> memory (key=0190, addr=018E): error code 487
> 2018-04-23 15:57:10.65
Greetings,
On Tue, Sep 3, 2019 at 19:38 David Fetter wrote:
> On Tue, Sep 03, 2019 at 03:56:28PM -0400, Stephen Frost wrote:
> > Greetings,
> >
> > * David Fetter (da...@fetter.org) wrote:
> > > I'd like to $Subject, on by default, with a switch to turn i
Greetings,
* Alvaro Herrera (alvhe...@2ndquadrant.com) wrote:
> On 2019-Sep-03, Stephen Frost wrote:
> > * David Fetter (da...@fetter.org) wrote:
> > > I'd like to $Subject, on by default, with a switch to turn it off for
> > > those really at the outer edges of p
Greetings,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Stephen Frost writes:
> > * Alvaro Herrera (alvhe...@2ndquadrant.com) wrote:
> >> I think there is a false dichotomy here. Migrating an extension out of
> >> contrib doesn't have to equate making it no lon
Greetings,
* Yuli Khodorkovskiy (yuli.khodorkovs...@crunchydata.com) wrote:
> On Tue, Sep 3, 2019 at 3:25 PM Stephen Frost wrote:
> > * Kohei KaiGai (kai...@heterodb.com) wrote:
> > > 2019年7月25日(木) 3:52 Yuli Khodorkovskiy
> > > :
> > > > Since all DAC che
Greetings,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Yuli Khodorkovskiy writes:
> > Ah, now I remember why I didn't add regressions to the original patch.
> > As stated at the top of the thread, the "db_table: { truncate }"
> > permission does not currently exist in refpolicy. A workaround would
>
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Thu, Sep 12, 2019 at 5:19 PM Tom Lane wrote:
> > However, if there is some character C that makes ICU misbehave like
> > that, we are going to have problems with indexing strings containing C,
> > whether we think varstr_cmp is leaky or
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Mon, Sep 16, 2019 at 4:31 AM Amit Kapila wrote:
> > Can we think of using creation time for file? Basically, if the file
> > creation time is later than backup-labels "START TIME:", then include
> > that file entirely. I think one big
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Mon, Sep 16, 2019 at 10:38 AM Stephen Frost wrote:
> > In a number of cases, trying to make sure that on a failover or copy of
> > the backup the next 'incremental' is really an 'incremental' is
&
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Mon, Sep 16, 2019 at 9:30 AM Robert Haas wrote:
> > > Isn't some operations where at the end we directly call heap_sync
> > > without writing WAL will have a similar problem as well?
> >
> > Maybe. Can you give an example?
>
> Looking
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Mon, Sep 16, 2019 at 1:10 PM Stephen Frost wrote:
> > I disagree with this on a couple of levels. The first is pretty simple-
> > we don't have all of the information. The user may have some reason to
> > be
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Mon, Sep 16, 2019 at 3:38 PM Stephen Frost wrote:
> > As discussed nearby, not everything that needs to be included in the
> > backup is actually going to be in the WAL though, right? How would that
> > ever be ab
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Tue, Sep 17, 2019 at 12:09 PM Stephen Frost wrote:
> > We need to be sure that we can detect if the WAL level has ever been set
> > to minimal between a full and an incremental and, if so, either refuse
> > to ru
Greetings,
* Peter Eisentraut (peter.eisentr...@2ndquadrant.com) wrote:
> On 2019-09-17 22:22, Tom Lane wrote:
> > Peter Eisentraut writes:
> >> * Add GSSAPI encryption support (Robbie Harwood, Stephen Frost)
> >> This allows TCP/IP connections to be
Greetings,
* David Steele (da...@pgmasters.net) wrote:
> On 9/28/19 1:26 PM, Fujii Masao wrote:
> > On Sun, Sep 29, 2019 at 12:51 AM David Steele wrote:
> >
> > Yeah, more checks would be necessary. IMO easy fix is to forbid not only
> > recovery target parameters but also any recovery parameter
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Mon, Sep 30, 2019 at 5:26 PM Bruce Momjian wrote:
> > For full-cluster Transparent Data Encryption (TDE), the current plan is
> > to encrypt all heap and index files, WAL, and all pgsql_tmp (work_mem
> > overflow). The plan is:
> >
> >
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Tue, Oct 1, 2019 at 12:19 PM Bruce Momjian wrote:
> > Just to give more detail. Initially, there was a desire to store keys
> > in only one place, either in the file system or in database tables.
> > However, it became clear that the n
Greetings,
* Tomas Vondra (tomas.von...@2ndquadrant.com) wrote:
> On Thu, Oct 03, 2019 at 10:40:40AM -0400, Stephen Frost wrote:
> >People who are looking for 'encrypt all the things' should and will be
> >looking at filesytem-level encryption options. That's not
Greetings,
* Peter Eisentraut (peter.eisentr...@2ndquadrant.com) wrote:
> On 2019-10-03 16:40, Stephen Frost wrote:
> >> As others have said, that sounds wrong to me. I think you need to
> >> encrypt everything.
> > That isn't what other database systems
Greetings,
* Tomas Vondra (tomas.von...@2ndquadrant.com) wrote:
> On Thu, Oct 03, 2019 at 11:51:41AM -0400, Stephen Frost wrote:
> >* Tomas Vondra (tomas.von...@2ndquadrant.com) wrote:
> >>On Thu, Oct 03, 2019 at 10:40:40AM -0400, Stephen Frost wrote:
> >>>People wh
Greetings,
* Tomas Vondra (tomas.von...@2ndquadrant.com) wrote:
> On Thu, Oct 03, 2019 at 11:58:55AM -0400, Stephen Frost wrote:
> >* Peter Eisentraut (peter.eisentr...@2ndquadrant.com) wrote:
> >>On 2019-10-03 16:40, Stephen Frost wrote:
> >>>> As others have
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Thu, Oct 3, 2019 at 1:29 PM Stephen Frost wrote:
> > I don't think I was arguing specifically about VM/FSM in particular but
> > rather about things which, for us, are cluster level. Admittedly, some
> >
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Mon, Oct 7, 2019 at 9:14 AM Fujii Masao wrote:
> > Agreed, too. Do you have any idea to implement that? I've not found out
> > "smart" way to do that yet.
> >
> > One idea is, as Michael suggested, to use SetConfigOption() for all the
>
Greetings,
* Anastasia Lubennikova (a.lubennik...@postgrespro.ru) wrote:
> Cool. It seems that everyone agrees on this patch.
Thanks for working on this, I took a quick look over it and I do have
some concerns.
> I attached the updated version. Now it prints a better error message
> and generate
Greetings,
* Fujii Masao (masao.fu...@gmail.com) wrote:
> On Tue, Oct 8, 2019 at 10:58 PM Stephen Frost wrote:
> > Having these options end up set but then hacking all of the other code
> > that looks at them to check if we're actually in recovery or not would
> > end
Greetings,
* Magnus Hagander (mag...@hagander.net) wrote:
> Unless we are *absolutely* certain, I bet someone will be able to find a
> side-channel that somehow leaks some data or data-about-data, if we don't
> encrypt everything. If nothing else, you can get use patterns out of it,
> and you can
Greetings,
* Martín Marqués (mar...@2ndquadrant.com) wrote:
> pg_last_wal_receive_lsn()
> pg_last_wal_replay_lsn()
> pg_last_xact_replay_timestamp()
>
> Under normal circumstances we would expect to receive NULLs from all
> three functions on a primary node, and code comments back up my thoughts.
Greetings,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Andrew Gierth writes:
> > "Tom" == Tom Lane writes:
> > Tom> Perhaps we could change the back branches so that they interpret
> > Tom> "-f -" as "write to stdout", but without enforcing that you use
> > Tom> that syntax.
>
> > We should def
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Tue, Oct 8, 2019 at 9:58 AM Stephen Frost wrote:
> > From a user
> > perspective, what happens when you've started up PG as a primary, since
> > you don't have a signal file in place to indicate that you
Greetings,
* Euler Taveira (eu...@timbira.com.br) wrote:
> Em ter, 8 de out de 2019 às 15:08, Stephen Frost
> escreveu:
> > * Tom Lane (t...@sss.pgh.pa.us) wrote:
> > > Andrew Gierth writes:
> > > > "Tom" == Tom Lane writes:
> > > > Tom&
Greetings,
* Fujii Masao (masao.fu...@gmail.com) wrote:
> On Wed, Oct 9, 2019 at 1:02 AM Stephen Frost wrote:
> > * Fujii Masao (masao.fu...@gmail.com) wrote:
> > > On Tue, Oct 8, 2019 at 10:58 PM Stephen Frost wrote:
> > > > Having these options end up set but
Greetings,
* Christoph Berg (m...@debian.org) wrote:
> Re: Tom Lane 2019-10-08 <9333.1570566...@sss.pgh.pa.us>
> > Having said all that, if we conclude we can't break compatibility
> > with this legacy code quite yet, I'd be inclined to put a
> > separate, clearly-marked-as-legacy-code version of
Greetings,
* Magnus Hagander (mag...@hagander.net) wrote:
> On Thu, Oct 3, 2019 at 4:40 PM Stephen Frost wrote:
> > * Robert Haas (robertmh...@gmail.com) wrote:
> > > On Mon, Sep 30, 2019 at 5:26 PM Bruce Momjian wrote:
> > > > For full-cluster Transparent Data
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Wed, Oct 9, 2019 at 8:42 AM Stephen Frost wrote:
> > If anything, what we should be doing here is throwing a WARNING or
> > similar that these settings don't make sense, because we aren't going
> > throu
Greetings,
* Craig Ringer (cr...@2ndquadrant.com) wrote:
> On Wed, 9 Oct 2019 at 22:30, Stephen Frost wrote:
> > - All decryption happens in a given backend when it's sending data to
> > the client
>
> That is not what I think of as TDE. But upon review, it looks
special meaning in v11 -
> > it
> > just writes a file called ./- And it's considered untennable to change
> > behavior of v11.
>
> Ahh... I totally missed thinking about the behavior of "-f -" in v11 when I
> reviewed this patch.
Clearly you wer
ore-or-less) to update the scripts to deal with
the v12 changes, but didn't like that those changes then broke when run
against v11, something that would be fixed by correcting those earlier
versions.
> On Wed, Oct 16, 2019 at 01:21:48PM -0400, Stephen Frost wrote:
> > [...] if they a
Greetings,
* Justin Pryzby (pry...@telsasoft.com) wrote:
> On Wed, Oct 16, 2019 at 03:04:52PM -0400, Stephen Frost wrote:
>
> > > On Wed, Oct 16, 2019 at 01:21:48PM -0400, Stephen Frost wrote:
> > > > [...] if they actually need to work with both concurrently
Greetings,
* Kyle Bateman (k...@batemans.org) wrote:
> What I hope to accomplish is: Establish a secure, encrypted connection to
> Postgresql from a trusted process, possibly running on another machine, whom
> I trust to tell me which user (within a limited set, defined by a role) it
> would like
Greetings,
* Justin Pryzby (pry...@telsasoft.com) wrote:
> On Thu, Oct 17, 2019 at 12:24:10PM +0200, Tom Lane wrote:
> > Alternatively, we could revoke the requirement to use "-f -" in 12,
> > and wait a couple releases before enforcing it. The fundamental
> > problem here is that we tried to go
Greetings,
* Thomas Munro (thomas.mu...@gmail.com) wrote:
> On Tue, Oct 8, 2019 at 11:09 PM Amit Kapila wrote:
> > I am personally still in the camp of people advocating the use of
> > macro for this purpose. It is quite possible after reading your
> > points, some people might change their opin
Greetings,
* Chapman Flack (c...@anastigmatix.net) wrote:
> On 10/18/19 08:18, Stephen Frost wrote:
> > I realize that I need to don some fireproof gear for suggesting this,
> > but I really wonder how much fallout we'd have from just allowing {} to
> > be used.. It&
Greetings,
* Andres Freund (and...@anarazel.de) wrote:
> On 2019-10-18 09:03:31 -0400, Stephen Frost wrote:
> > * Chapman Flack (c...@anastigmatix.net) wrote:
> > > On 10/18/19 08:18, Stephen Frost wrote:
> > > > I realize that I need to don some fireproof gear for
Greetings,
* Isaac Morland (isaac.morl...@gmail.com) wrote:
> That embeds a temporary hack in the application code indefinitely.
... one could argue the same about having to say AS MATERIALIZED.
Thanks,
Stephen
signature.asc
Description: PGP signature
Greetings,
* Joe Nelson (j...@begriffs.com) wrote:
> > Is it possible to define the macro to be {} where supported and {0}
> > where needed? Something like:
>
> If it's being put behind a macro then *stylistically* it shouldn't
> matter whether {} or {0} is chosen, right? In which case {0} would
Greetings,
* Devrim Gündüz (dev...@gunduz.org) wrote:
> On Tue, 2019-10-22 at 19:16 +0900, Michael Paquier wrote:
> > You are referring to the connection string generated in
> > primary_conninfo here, right?
>
> Right.
I'm awful suspicious that there's other similar cases beyond this
particular
Greetings,
* Michael Paquier (mich...@paquier.xyz) wrote:
> On Tue, Oct 22, 2019 at 09:06:03AM -0400, Stephen Frost wrote:
> > Here's just a quick rough-up of a patch (it compiles, I haven't tried it
> > out more than that) that adds in a check to skip gssencmode on o
Greetings,
* Michael Paquier (mich...@paquier.xyz) wrote:
> On Tue, Oct 22, 2019 at 09:53:45AM -0400, Stephen Frost wrote:
> > Yeah.. Something along those lines definitely seems like it'd be better
> > as that would force anyone adding new options to explicitly say which
&g
Greetings,
* Bruce Momjian (br...@momjian.us) wrote:
> On Thu, Oct 10, 2019 at 10:40:37AM -0400, Stephen Frost wrote:
> > > Some people ask for indexable encrypted columns, but I tend to explain to
> > > them how impractical and inefficient that is. You can support hash index
Greetings,
* Fujii Masao (masao.fu...@gmail.com) wrote:
> On Wed, Feb 27, 2019 at 4:35 PM Laurenz Albe wrote:
> >
> > Fujii Masao wrote:
> > > So, let me clarify the situations;
> > >
> > > (3) If backup_label.pending exists but recovery.signal doesn't, the server
> > >ignores (or removes
Greetings,
I'm pleased to announce that we have been accepted by Google to
participate in the Summer of Code (GSoC) 2019 program. This will be the
12th time that the PostgreSQL Project will provide mentorship for
students to help develop new features for PostgreSQL. We have the chance
to accept st
Greetings,
* Michael Banck (michael.ba...@credativ.de) wrote:
> Am Freitag, den 01.03.2019, 18:03 -0500 schrieb Robert Haas:
> > On Tue, Sep 18, 2018 at 10:37 AM Michael Banck
> > wrote:
> > > I have added a retry for this as well now, without a pg_sleep() as well.
> > > This catches around 80% o
Greetings,
* Sumukha Pk (sumukhap...@gmail.com) wrote:
> I am Sumukha PK a student of NITK. I am interested in the WAL-G backup tool.
> I haven’t been able to catch hold of anyone through the IRC channels so I
> need someone to point me to appropriate resources so that I can be introduced
> to
Greetings,
On Tue, Mar 5, 2019 at 18:36 Michael Paquier wrote:
> On Tue, Mar 05, 2019 at 02:08:03PM +0100, Tomas Vondra wrote:
> > Based on quickly skimming that thread the main issue seems to be
> > deciding which files in the data directory are expected to have
> > checksums. Which is a valid
Greetings,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Mon, Mar 11, 2019 at 10:39 PM Michael Paquier wrote:
> > On Mon, Mar 11, 2019 at 06:32:10PM -0700, Jeff Davis wrote:
> > > * Is the original idea of a special role still viable?
> >
> > In my opinion, that part may be valuable. The la
Greetings!
* Robbie Harwood (rharw...@redhat.com) wrote:
> Stephen Frost writes:
> > * Peter Eisentraut (peter.eisentr...@2ndquadrant.com) wrote:
> >> Or maybe we avoid that, and you rename be-secure-gssapi.c to just
> >> be-gssapi.c and also combine that with the
Greetings,
* Tomas Vondra (tomas.von...@2ndquadrant.com) wrote:
> On 3/2/19 12:03 AM, Robert Haas wrote:
> > On Tue, Sep 18, 2018 at 10:37 AM Michael Banck
> > wrote:
> >> I have added a retry for this as well now, without a pg_sleep() as well.
> >> This catches around 80% of the half-reads, but
Greetings,
* Tomas Vondra (tomas.von...@2ndquadrant.com) wrote:
> If we want to run it from the server itself, then I guess a background
> worker would be a better solution. Incidentally, that's something I've
> been toying with some time ago, see [1].
So, I'm a big fan of this idea of having a b
Greetings,
* Andres Freund (and...@anarazel.de) wrote:
> On 2019-03-12 14:42:14 +0900, Michael Paquier wrote:
> > On Mon, Mar 11, 2019 at 08:38:56PM +, Regina Obe wrote:
> > > I tested on windows mingw64 (as of a week ago) and confirmed the
> > > patch applies cleanly and significantly faster
401 - 500 of 1955 matches
Mail list logo
