On Tue, Dec 5, 2017 at 09:23:49AM -0500, Stephen Frost wrote:
> Dave,
>
> * Dave Page (dp...@pgadmin.org) wrote:
> > On Tue, Dec 5, 2017 at 11:01 PM, Bruce Momjian <br...@momjian.us> wrote:
> > > As part of PGConf.Asia 2017 in Tokyo, we had an unconference t
he bad news is that only a small percentage of users
who will benefit from it will use it, and some who will not benefit it
will use it. Also, this is going to require significant server changes,
which have to be maintained.
I think we need some statistics on how many users ar
ext
respresentation of data type, but at this point it might be worth it.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
On Fri, Dec 8, 2017 at 12:26:55PM -0500, Stephen Frost wrote:
> 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
> >
On Tue, Dec 5, 2017 at 11:16:26PM +0900, Dave Page wrote:
> Hi
>
> On Tue, Dec 5, 2017 at 11:01 PM, 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 dis
?
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
On Sun, May 13, 2018 at 04:55:35PM +0530, Amit Kapila wrote:
> On Sun, May 13, 2018 at 4:40 PM, Amit Kapila <amit.kapil...@gmail.com> wrote:
> > On Fri, May 11, 2018 at 8:38 PM, Bruce Momjian <br...@momjian.us> wrote:
> >> I have committed the first draft of the
On Mon, May 14, 2018 at 05:34:54PM +0530, Dilip Kumar wrote:
>
> On Fri, May 11, 2018 at 8:38 PM, Bruce Momjian <br...@momjian.us> wrote:
>
> I have committed the first draft of the Postgres 11 release notes. I
> will add more markup soon. You can view the most
On Sun, May 13, 2018 at 06:53:26PM +0900, Amit Langote wrote:
> On Sat, May 12, 2018 at 12:08 AM, Bruce Momjian <br...@momjian.us> wrote:
> > I have committed the first draft of the Postgres 11 release notes. I
> > will add more markup soon. You can view the most
On Mon, May 14, 2018 at 07:47:54AM -0400, Andrew Dunstan wrote:
>
>
> On 05/12/2018 08:47 PM, Bruce Momjian wrote:
> > On Sat, May 12, 2018 at 01:22:55PM -0700, Peter Geoghegan wrote:
> >> On Fri, May 11, 2018 at 2:06 PM, Bruce Momjian <br...@momjian.us> wrote:
>
On Sun, May 13, 2018 at 03:43:08PM +0900, Michael Paquier wrote:
> On Fri, May 11, 2018 at 11:08:52AM -0400, Bruce Momjian wrote:
> > I have committed the first draft of the Postgres 11 release notes. I
> > will add more markup soon. You can view the most current version
> &
On Mon, May 14, 2018 at 07:10:18AM -0400, David Steele wrote:
> On 5/13/18 8:26 PM, Michael Paquier wrote:
> > On Sun, May 13, 2018 at 03:43:08PM +0900, Michael Paquier wrote:
> >> On Fri, May 11, 2018 at 11:08:52AM -0400, Bruce Momjian wrote:
> >>> I have committed t
On Mon, May 14, 2018 at 09:26:07AM +0900, Michael Paquier wrote:
> On Sun, May 13, 2018 at 03:43:08PM +0900, Michael Paquier wrote:
> > On Fri, May 11, 2018 at 11:08:52AM -0400, Bruce Momjian wrote:
> > > I have committed the first draft of the Postgres 11 release notes. I
&
On Sun, May 13, 2018 at 05:43:25PM +0900, Đặng Minh Hướng wrote:
> Hello Bruce,
>
> Thanks for the greate work!
>
> 2018-05-12 0:08 GMT+09:00 Bruce Momjian <br...@momjian.us>:
>
> I have committed the first draft of the Postgres 11 release notes. I
> will
On Sun, May 13, 2018 at 04:40:19PM +0530, Amit Kapila wrote:
> On Fri, May 11, 2018 at 8:38 PM, Bruce Momjian <br...@momjian.us> wrote:
> > I have committed the first draft of the Postgres 11 release notes. I
> > will add more markup soon. You can view the most
On Tue, May 15, 2018 at 08:10:20AM +0900, Michael Paquier wrote:
> On Mon, May 14, 2018 at 04:04:58PM -0400, Bruce Momjian wrote:
> > So, channel binding has had me confused since I first heard about it. I
> > have done some research and reworded the commit with the attached
reund
> Discussion:
> https://postgr.es/m/20170222.115044.1665674502985097185.t-is...@sraoss.co.jp
That seemed too detailed for the release notes. Is that wrong?
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
> XML but also the build system to XSL. The latter is out of the
> question, I think.
Why is that? I thought people building current Postgres would already
have the XML toolchain built to build older release documentation.
--
Bruce Momjian <br...@momjian.us>http://momjian
nd. We need this too when sync replication fails.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
On Fri, Apr 27, 2018 at 04:10:43PM -0700, Andres Freund wrote:
> Hi,
>
> On 2018-04-27 19:04:47 -0400, Bruce Momjian wrote:
> > On Fri, Apr 27, 2018 at 03:28:42PM -0700, Andres Freund wrote:
> > > - We need more aggressive error checking on close(), for ENOSPC and
&g
On Sat, May 12, 2018 at 01:22:55PM -0700, Peter Geoghegan wrote:
> On Fri, May 11, 2018 at 2:06 PM, Bruce Momjian <br...@momjian.us> wrote:
> > Done and URL updated.
>
> I have some feedback on "Allow NOT NULL to be added to columns without
> requirin
championing
two features that I think have strategic significance but didn't make it
into Postgres 11: parallel FDW access and improved multi-variate
statistics. I hope to do better job during Postgres 12.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
Enterp
On Fri, May 11, 2018 at 07:49:50PM +0300, Teodor Sigaev wrote:
>
>
> Bruce Momjian wrote:
> >I have committed the first draft of the Postgres 11 release notes. I
> >will add more markup soon. You can view the most current version here:
> >
> > http://momj
ures that I think have strategic significance but didn't make it
> >into Postgres 11: parallel FDW access and improved multi-variate
> >statistics.
>
> I'm planning to try to help with the later.
Great, thanks.
--
Bruce Momjian <br...@momjian.us>http://momjian.u
On Fri, May 11, 2018 at 01:40:54PM -0400, Chapman Flack wrote:
> On 05/11/2018 11:08 AM, Bruce Momjian wrote:
>
> > http://momjian.us/pgsql_docs/release-11.html
> >
> > I expect a torrent of feedback. ;-)
>
> Very superficial things:
>
>
> Add pr
On Fri, May 11, 2018 at 11:50:51AM -0700, Andres Freund wrote:
> On 2018-05-11 14:44:06 -0400, Bruce Momjian wrote:
> > On Fri, May 11, 2018 at 07:49:50PM +0300, Teodor Sigaev wrote:
> > >
> > >
> > > Bruce Momjian wrote:
> > > >I have committed
On Fri, May 11, 2018 at 04:00:58PM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > OK, so what is the text that people will understand? This?
> >
> > Prevent manual VACUUMs on append-only tables from performing
> > needless index scans
>
> >
> >
> >
>
> I wonder if we shouldn't omit those, considering them part of the JIT
> entry? Not quite sure what our policy there is.
OK, removed.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
> replacement selection sort algorithm is no longer used."
>
> Also, it should be moved to "Migration to Version 11", since the only
> issue here is compatibility with older versions.
Done.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB
" should specify that it only
> works for B-Tree index builds.
>
> * Suggest replacement sort item be phrased as: "Remove the
> configuration parameter replacement_sort_tuples. The
> replacement selection sort algorithm is no longer used."
All done.
--
Bruce
or from json(b)
> >
> >OK, how is this text?
> >
> > Add function json(b)_to_tsvector() to create
> > text search query for matching JSON/JSONB
> > values (Dmitry Dolgov)
> Not query - *_to_tsvector functions produce a tsvector. So:
>
tion decline from new developers is based on
our build system, and how much of it is based on the fact we use the C
language?
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am,
On Wed, May 16, 2018 at 09:09:22PM -0400, Bruce Momjian wrote:
> > > FYI, I think the server could also require channel binding for SCRAM. We
> > > already have scram-sha-256 in pg_hba.conf, and I think
> > > scram-sha-256-plus would be reasonable.
> >
>
On Thu, May 17, 2018 at 09:48:54PM +0900, Michael Paquier wrote:
> On Wed, May 16, 2018 at 09:09:22PM -0400, Bruce Momjian wrote:
> > On Thu, May 17, 2018 at 09:56:49AM +0900, Michael Paquier wrote:
> >> On Wed, May 16, 2018 at 08:20:49PM -0400, Bruce Momjian wrote:
> &
d about release notes.
Agreed. The problem was so glaring that I assumed I was not
understanding it. I have modified this email subject so users will
hopefully read back in this thread to see the details.
--
Bruce Momjian <br...@momjian.us>http://momj
On Thu, May 17, 2018 at 10:35:53PM +0900, Michael Paquier wrote:
> Hi Bruce,
>
> Here is some bonus feedback.
>
> On Fri, May 11, 2018 at 11:08:52AM -0400, Bruce Momjian wrote:
> > I expect a torrent of feedback. ;-)
>
> I have just noticed that this entry does
On Tue, May 15, 2018 at 06:40:18AM +, Huong Dangminh wrote:
> Hi,
>
> > From: David Rowley [mailto:david.row...@2ndquadrant.com]
> > Sent: Tuesday, May 15, 2018 3:01 PM
> > To: Bruce Momjian <br...@momjian.us>
> > Cc: Đặng Minh Hướng <kakalo...@gmail.
On Tue, May 15, 2018 at 02:26:33PM +0900, Etsuro Fujita wrote:
> (2018/05/12 0:08), Bruce Momjian wrote:
> >I have committed the first draft of the Postgres 11 release notes. I
> >will add more markup soon. You can view the most current version here:
> >
> > h
Allow single-evaluation queries, e.g. FROM
clause queries, and functions in the target list to be
parallelized (Amit Kapila, Robert Haas)
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
@sraoss.co.jp
> >
> > That seemed too detailed for the release notes. Is that wrong?
>
> This commit gives user-visible changes to the statment timeout
> behavior. So I think this should be added to the release notes.
OK, makes sense. Here is what I added:
2017-09-1
On Tue, May 15, 2018 at 01:04:55PM +0530, Amit Kapila wrote:
> On Tue, May 15, 2018 at 11:43 AM, David Rowley
> <david.row...@2ndquadrant.com> wrote:
> > On 12 May 2018 at 03:08, Bruce Momjian <br...@momjian.us> wrote:
> >> I have committed the first draft of
On Wed, May 16, 2018 at 01:22:45PM +0900, Michael Paquier wrote:
> On Mon, May 14, 2018 at 08:45:44PM -0400, Bruce Momjian wrote:
> > What TLS does is to mix the offered ciphers into the negotiation hash so
> > a man-in-the-middle can't pretend it doesn't support something.
On Mon, May 21, 2018 at 06:28:36PM +1000, Haribabu Kommi wrote:
> On Sat, May 12, 2018 at 1:08 AM, Bruce Momjian <br...@momjian.us> wrote:
>
> I have committed the first draft of the Postgres 11 release notes. I
> will add more markup soon. You can view the most cu
On Sat, May 19, 2018 at 12:58:04AM +0900, Amit Langote wrote:
> Hi Bruce.
>
> On Tue, May 15, 2018 at 12:46 PM, Amit Langote
> <langote_amit...@lab.ntt.co.jp> wrote:
> > On 2018/05/15 5:30, Bruce Momjian wrote:
> >> I like it, done.
> >
> > Thank you.
faster, but adding rows to
partitioned tables with many partitions is still slow, got it.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
.8k tps, which I'll submit for PG12. I'm unsure if we should be
Yikes! I think the question is whether we need to _remove_ the item I
just posted that is already in the release notes:
Allow faster partition elimination during query processing (Amit
Langote, David Rowley, Di
r ARMv8 hardware
> CRC calculations (Yuqi Gu, Heikki Linnakangas)
>
>
> Could I please ask for a third author credit for this one? See
> commits 1c72ec6 (and follow-up a7a7387) which extended ARM CRC support
> to non-Linux systems.
Done.
--
Bruce Momjian <br...@
On Wed, May 23, 2018 at 11:55:29AM +1000, Haribabu Kommi wrote:
> Yes, security labels also gets dumped only with --create option.
OK.
> Can you update the author name as (Haribabu Kommi) to make it consistent
> with other entries.
Done. Applied patch attached.
--
Bruce Mom
On Wed, May 23, 2018 at 02:06:15PM +1200, David Rowley wrote:
> On 23 May 2018 at 13:18, Bruce Momjian <br...@momjian.us> wrote:
> > On Mon, May 21, 2018 at 07:34:18PM +1200, David Rowley wrote:
> >> I've been working a bit in this area over the past few weeks and w
age type, which is
> something that we know about as the exchange state is saved in
> PGconn->sasl_state.
I had not thought of 'trust'. I was more worried about the password
hash being downgraded in robustness or passed through a
man-in-the-middle, while the 'trust' does not require. However, yo
>
Date: Tue Feb 13 18:52:21 2018 -0500
Make plpgsql use its DTYPE_REC code paths for composite-type
variables.
Sure I can add it, once you confirm.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB
On Sat, May 19, 2018 at 09:35:57PM +0900, Michael Paquier wrote:
> On Fri, May 18, 2018 at 09:30:22AM -0400, Bruce Momjian wrote:
> > Good work, but I think the existance of both scram_channel_binding and
> > channel_binding_mode in libpq is confusing. I am thinking we should
>
rging them into a single
options seems unwise, as Magnus mentioned.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
On Tue, May 22, 2018 at 11:31:08PM -0400, Tom Lane wrote:
> Bruce Momjian <br...@momjian.us> writes:
> > On Fri, May 18, 2018 at 10:28:12AM -0400, Tom Lane wrote:
> >> While we're all griping about omissions from the release notes ...
> >> I think you should have
(!defined($ENV{TZ}) || $ENV{TZ} =~ m/^E.T$/))
which just looks odd to me. Am I the only person who often does this?
The second option, --break-after-all-operators, is more of a personal
taste, but it does match how our C code works, and people have said I
write C code in Perl. ;-)
--
Bruce Momj
sane apprach? Are there other ideas?
Do we really know someone is going to want to actually specify the
channel binding type? If it is only testing, maybe we don't need to
document this parameter.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
er happen, causing performance
> to tank.
I would love to know how we can help people find out how much data is in
each of these rings so they can tune shared buffers accordingly.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB
. So maybe you're both right
> and it's overkill to have it. I'm not set on having it, either. Does
> anybody else have an opinion?
>
>
> I toss my +1 to removing it altogether.
+1 We are terrible at removing old GUCs and having it around means
everyone has
On Thu, May 24, 2018 at 02:23:17PM -0400, Alvaro Herrera wrote:
> On 2018-May-24, Bruce Momjian wrote:
>
> > On Wed, May 2, 2018 at 07:49:42PM -0700, David G. Johnston wrote:
>
> > > I toss my +1 to removing it altogether.
> >
> > +1 We are terrible at re
now return 1234. L and TH now only consume characters
that are not digits, positive/negative signs, decimal points,
and commas.
so I think we are consistent in ignoring invalid input characters so I
would we would change it.
I am not sure adding documentation would really help much.
--
Bru
,
"tls-unique", "tls-server-end-point", and "require". I don't see the
point to having "none" and "allow" that sslmode supports. "tls-unique"
and "tls-server-end-point" would _require_ those channel binding modes;
the settin
On Fri, May 18, 2018 at 10:56:25AM +0500, Andrey Borodin wrote:
> H, Bruce!
>
>
> 11 мая 2018 г., в 20:08, Bruce Momjian <br...@momjian.us> написал(а):
>
> I expect a torrent of feedback. ;-)
>
>
> I'm not sure it is usefull in release
ot;better performance", and I think
> Bruce's opinion of what's a documentable feature is biased against
> including that type of change. So that might account for some of
> these numbers, too.
It probably is biased, but hopefully consistently so --- that would
explain the decline
ill always imply a lot of "OS like" infrastructure.
>
I think threading would definitely make server programming harder.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so
tion background workers instead?
> >
> > Change the ps process display labels for background workers
> > to match the pg_stat_activity.backend_type labels Eisentraut)
>
> Seems good to me.
Done.
--
Bruce Momjian <br...@momjian.us>
On Wed, May 16, 2018 at 09:01:35AM +0900, Tatsuo Ishii wrote:
> There's a small typo.
>
> > Add support for with huge(large) pages on Windows (Takayuki Tsunakawa,
> > Thomas Munro)
>
> I think a space between "huge" and "(large)" is needed.
binding_mode that we want to control at the client. The lesser
modes are much more reasonable to use an automatic best-supported
negotiation, which is what we do now.
FYI, I think the server could also require channel binding for SCRAM. We
already have scram-sha-256 in pg_hba.conf, and I think
scram-sha
On Wed, May 16, 2018 at 10:08:18AM -0400, Alvaro Herrera wrote:
> On 2018-May-15, Bruce Momjian wrote:
>
> > On Wed, May 16, 2018 at 09:01:35AM +0900, Tatsuo Ishii wrote:
> > > There's a small typo.
> > >
> > > > Add support for with huge(l
On Wed, May 16, 2018 at 09:55:05AM +0530, Amit Kapila wrote:
> On Wed, May 16, 2018 at 12:17 AM, Bruce Momjian <br...@momjian.us> wrote:
> > On Tue, May 15, 2018 at 08:45:07AM +0530, Amit Kapila wrote:
> >> No, it is not like that. We divide the scan among workers and
suggest rewording this:
>
> * Allow server options related to memory and file sizes, to be specified as
> number of bytes.
>
> The new unit is "B". This is in addition to "kB", "MB", "GB" and "TB", which
> were accepted prev
On Thu, May 17, 2018 at 09:56:49AM +0900, Michael Paquier wrote:
> On Wed, May 16, 2018 at 08:20:49PM -0400, Bruce Momjian wrote:
> > SCRAM-with-binding is the first password method that attempts to avoid
> > man-in-the-middle attacks, and therefore is much less likely to be able
&g
Ishii)
>
> Can you please add Andres Freund to the author? He made extensive
> changes to the original patch to improve it.
Done.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
sentraut)"
Good point. Should we mention background workers instead?
Change the ps process display labels for background workers
to match the pg_stat_activity.backend_type labels Eisentraut)
--
Bruce Momjian <br...@momjian.us>http://momjian.us
Enterprise
not perfectly accurate.
One reason the PG 11 count is lower is because the the major items for
this release are not listed at the top yet, but that is only around six
items.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprise
On Thu, May 17, 2018 at 05:01:17PM -0700, Andres Freund wrote:
> On 2018-05-17 19:56:43 -0400, Tom Lane wrote:
> > David Rowley <david.row...@2ndquadrant.com> writes:
> > > On 18 May 2018 at 11:29, Bruce Momjian <br...@momjian.us> wrote:
> > >> I regu
ut session. If not, and that is
what makes swapping session state make Postgres faster, let's just find
a way to skip checking visibility rules for inactive sessions and get
the same benefit more simply.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB
/master;hp=586e4e6df5b85ddd28c9e881d237bd7380ffeb8e
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
Should we remove the patch?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
to help setting
> up a test environment?
>
> I have at hand only a Debian installation, and I have just guessed the
> RHEL and FreeBSD dependencies.
Patch applied to head, thanks.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterpr
ant to add a value to a
> balance without being able to read the balance and learn the current value. I
> haven't heard of it being used for searches before.
I have a slide about indexing encrypted data; not sure if it is
relevant:
https://momjian.us/main/writings/crypto_hw_use.pdf#pag
e removed. I added them years ago in
case they helped anyone else.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
t; for how to apply them and huge amounts of maintenance effort), but as a
> communications tool I'd say email is vastly superior, particularly thanks to
> the flexibility.
It might be that occasional uses would find github easier, and more
invested users would find email easier.
--
B
; references to the GUC will have dashes rather than underscores, plus
> possibly other variations.
Yes, I even check the docs after whitespace changes.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I.
r language has
> a time-with-zone-in-offset-form data type.
>
> Speaking of time zones, what PLs out there have a notion of time zone
> maintained by their language runtimes, and how many of those use the
> PostgreSQL session_timezone to initialize that?
That's a good question.
On Fri, Jun 22, 2018 at 01:28:58PM -0500, Merlin Moncure wrote:
> On Fri, Jun 22, 2018 at 12:34 PM Bruce Momjian wrote:
> >
> > What we don't want to do is to add a bunch of sharding-specific code
> > without knowing which workloads it benefits, and how many of our users
On Sat, Jun 23, 2018 at 12:41:00PM +1000, Haribabu Kommi wrote:
>
> On Sat, Jun 23, 2018 at 12:17 PM Bruce Momjian wrote:
>
> On Fri, Jun 22, 2018 at 01:28:58PM -0500, Merlin Moncure wrote:
> > On Fri, Jun 22, 2018 at 12:34 PM Bruce Momjian wrote:
> > >
&
Channel binding's sole value
is to prevent such attacks, so if it cannot prevent them, it has no use
and will just confuse people until we make it useful in a later release.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://ent
sharding-specific code will have the greatest impact.
What we don't want to do is to add a bunch of sharding-specific code
without knowing which workloads it benefits, and how many of our users
will actually use sharding. Some projects have it done that, and it
didn't end well since they then had a l
https://www.theregister.co.uk/2018/03/27/with_tls_13_signed_off_its_implementation_time/
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman
On Sat, Jun 23, 2018 at 10:30:19PM +0900, Michael Paquier wrote:
> On Fri, Jun 22, 2018 at 11:01:53PM -0400, Bruce Momjian wrote:
> > Uh, as I am understanding it, if we don't allow clients to force channel
> > binding, then channel binding is useless because it cannot
com
>
> Thanks a lot!
>
> It seems that other people need that feature too. :-)
>
> I will try to apply and review the patch.
Uh, no one mentioned in this thread that psql has supported asciidoc
since PG 9.5.
--
Bruce Momjian http://momjian.us
EnterpriseDB
ldBuildSnapshot().
>
> Interesting. While this sounds like an oversight that should have
> horrible consequences, it's seems not to because the current callers
> don't seem to care about the ->satisfies function. Are you able to come
> up with some scenario in which it causes an a
xplicitly mentioned in the docs.
> How about the attached patch?
OK, doc patch added to git head. Let me know if I should back patch it
further. Thanks.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I
paces, etc.
I would love to see an API that allowed hypothetical indexes too.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
how rare this is, this is probably the cleanest solution, and I
think can be backpatched.
Patch attached.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient
On Thu, Jun 21, 2018 at 07:42:54AM +0530, Amit Kapila wrote:
> On Wed, Jun 20, 2018 at 8:47 PM, Bruce Momjian wrote:
> > On Sat, Jun 2, 2018 at 05:18:17PM -0400, Asim Praveen wrote:
> >> Hi Amit
> >>
> >> On Mon, May 28, 2018 at 4:25 AM, Amit Kapila
>
pg_waldump output?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
e IV used for each block to be a mixture of the table's IV and the
page's offset in the table.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Ro
Vault
> for example, or maybe something self contained, or perhaps both. Or
> maybe key management is really tied into the separately discussed effort
> to create SQL VARIABLEs somehow.
I cover key management in this slide, and following:
http://momjian.us/main/writings/cry
really can't identify much except the length, as Robert stated.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
1 - 100 of 2568 matches
Mail list logo
