-temporary and/or non-unlogged tables.
--
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, Jun 4, 2017 at 02:30:58PM -0400, Tom Lane wrote:
> Bruce Momjian <br...@momjian.us> writes:
> > I didn't want to optimize for it --- I wanted a way to detect when DROP
> > EXTENSION has no hope of working, and give more details. I assume the
> > problem with t
On Sun, Jun 4, 2017 at 02:04:37PM -0400, Tom Lane wrote:
> Bruce Momjian <br...@momjian.us> writes:
> > The problem is that in some cases extensions are improperly removed or
> > the extension has bugs that leaves pg_proc entries around that aren't
> > dumped,
pg_proc entries around that aren't
dumped, but are seen by pg_upgrade and generate an error. In these
cases, and I have seen a few recently, we don't give the user any way to
find the cause except ask for assistance, i.e. we don't show them the
query we used to find the problem libraries.
--
Bru
On Sun, Jun 4, 2017 at 01:20:12PM -0400, Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > I have seen a few reports where people are getting this pg_upgrade
> > error:
> >
> > Your installation references loadable libraries that are missing
> > from t
This seems to be one of the last pg_upgrade problems, along with
preserving optimizer statistics, which I am hoping to do for PG 11.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so on
work to implement.
TODO item added:
Allow tablespaces on RAM-based partitions for temporary objects
and I wrote a blog entry about this:
https://momjian.us/main/blogs/pgblog/2017.html#June_2_2017
--
Bruce Momjian <br...@momjian.us>http://momjian.us
Enterprise
k, exactly how does channel binding work? Is each side
of the SSL connection hashing the password hash with the shared SSL
session secret in some way that each side knows the other end knows
the password hash, but not disclosing the secret or password hash? Is
there some other way JDBC can get that
em, and since they are not in WAL and autovacuum can't see them,
their non-existence in a temporary tablespace would not be a problem.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterpris
On Wed, May 31, 2017 at 07:53:53AM -0400, Robert Haas wrote:
> On Tue, May 30, 2017 at 6:50 PM, Mark Dilger <hornschnor...@gmail.com> wrote:
> >> On May 29, 2017, at 11:53 AM, Bruce Momjian <br...@momjian.us> wrote:
> >> Right now we don't document that temp_tab
ot;ecpg/ecpglib/pg_type.h" file or not?
>
> It's not too big a deal as neither of the new OIDs is used in ecpg, but
> still, the file should be up to date.
>
> Thanks for the patch, committed.
Should we add some Makefile magic to make sure they stay in sync?
--
Bruce Momjia
Add UNIQUE capability to hash indexes
then when I got to your suggestion at the bottom, it was already done.
:-)
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, s
0...@joeconway.com
and later references to the report from Joe Conway (2005):
https://postgr.es/m/425ABB17.305%40joeconway.com
and you (2007):
https://postgr.es/m/18897.1197775682%40sss.pgh.pa.us
--
Bruce Momjian <br...@momjian.us>http://m
Right now we don't document that temp_tablespaces can use
non-restart-safe storage, e.g. /tmp, ramdisks. Would this be safe?
Should we document this?
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+
I have written the following sed script to convert regular Postgres
email message URLs to their shorter form for commit messages:
sed 's;http\(s\?\)://www\.postgresql\.org/message-id/;http\1://postgr.es/m/;gi'
in case this is helpful to anyone.
--
Bruce Momjian <br...@momjian
ode, which was designed
to improve code clarity, was so confusingly written. I went with the
sed script (and later Perl script) wrapper solution because the BSD
indent code was so confusing to me.
It seems like a "The Cobbler's children have no shoes" syndrome:
https://english.st
On Sun, May 21, 2017 at 09:11:29AM +0530, Amit Kapila wrote:
> On Sun, May 21, 2017 at 5:26 AM, Bruce Momjian <br...@momjian.us> wrote:
> > On Fri, May 19, 2017 at 04:54:27PM -0400, Robert Haas wrote:
> >> On Tue, May 16, 2017 at 9:25 AM, Amit Kapila <amit.kapi
reused some of my code from the 8.3-8.4 migration
in pg_upgrade that was removed a while back, rather than writing it from
scratch, right?
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are
't mess
> up his workflow.
You can commit it yourself, but I removed the first item earlier today
in a commit.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once wa
ease-10.sgml.
> Please find the attached patch.
Patch applied. Sorry I missed this. I must have been so focused on
how to add the item that I forgot the commit details.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterpris
ion of perltidy and I added a download
link to pgindent/README.
--
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 g
On Tue, May 16, 2017 at 09:00:38PM -0400, Bruce Momjian wrote:
> On Tue, May 16, 2017 at 08:39:36PM -0400, Tom Lane wrote:
> > Andres Freund <and...@anarazel.de> writes:
> > > There we go:
> > > https://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=ca
> > We use the same technique in other places such as pg_dump's help() too.
>
> Meh. Well, I reverted the changes in question while we discuss it.
Are we ready for a pgindent run now?
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB
On Tue, May 16, 2017 at 06:06:35PM -0700, Andres Freund wrote:
> On 2017-05-16 21:02:19 -0400, Tom Lane wrote:
> > Bruce Momjian <br...@momjian.us> writes:
> > > OK, I assume we are good to go for Wednesday afternoon, UTC. Thanks for
> > > the research.
> >
t; sure seems like a poor choice for a globally visible typedef name.
OK, I assume we are good to go for Wednesday afternoon, UTC. Thanks for
the research.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://en
On Mon, May 15, 2017 at 07:32:30AM -0700, Jeff Davis wrote:
> On Sun, May 14, 2017 at 8:00 PM, Bruce Momjian <br...@momjian.us> wrote:
> > Do we even know that floats are precise enough to determine the
> > partition. For example, if you have 6.
e 5.999 on some systems? Are IEEE systems all the same for
these values? I would say we should disallow any approximate date type
for partitioning completely.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As
es every so often. It'd be
> great if Bruce has time to do another round before Monday, but the
> current situation is not really broken.
Done. Applied patch attached.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://ent
I would like to run pgindent on the head source tree this Wednesday
afternoon, UTC. Is that OK for everyone?
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am,
ueries can be materialized,
so doing #1 means INLINE would be only a preference, which could be
confusing
Anyway, I am very glad we are considering addressing this in PG 11.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http
On Fri, May 12, 2017 at 08:35:26PM +0300, Konstantin Knizhnik wrote:
>
>
> On 12.05.2017 18:23, Bruce Momjian wrote:
> >On Fri, May 12, 2017 at 10:50:41AM +0300, Konstantin Knizhnik wrote:
> >>Definitely changing session context (search_path, date/time format, ...)
going to want global and local caches because
the plans of the local cache are much more likely to be accurate.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you wi
tifers, e.g. table and column names, so you
can't be sure it is the same as the cached entry you matched. I suppose
if you cleared the cache every time someone created an object or changed
search_path, it might work.
--
Bruce Momjian <br...@momjian.us>http://m
This split would also not work if the scanner feeds changes back into
the parser. I know C does that for typedefs but I don't think we do.
Ideally I would like to see percentage-of-execution numbers for typical
queries for scan, parse, parse-analysis, plan, and execute to see where
the wins are.
operator that has higher
precedence in the query could change the plan, though am not sure if
our prepared query system even handles that properly.
Anyway, that is my feedback. I would like to get an overview of what
you are trying to do and the costs/benefits of each option so we can
best gu
On Mon, May 1, 2017 at 08:12:51AM -0400, Robert Haas wrote:
> On Tue, Apr 25, 2017 at 10:16 PM, Bruce Momjian <br...@momjian.us> wrote:
> > Well, we could add "MD5 users are encouraged to switch to
> > SCRAM-SHA-256". Now whether we want to list this as som
gt; the patch later today if I don't hear additional comments.
> >
> >> For the record, I also voted for doing nothing.
> >
> > Hm, well, anybody else want to vote?
>
> +1 for #2
Same, +1 for #2 (apply this patch)
--
Bruce Momjian <br...@momjian.us>
On Mon, May 8, 2017 at 12:18:54PM +0900, Masahiko Sawada wrote:
> On Fri, May 5, 2017 at 8:38 AM, Bruce Momjian <br...@momjian.us> wrote:
> > On Fri, Apr 28, 2017 at 01:12:34PM +0900, Masahiko Sawada wrote:
> >> On Tue, Apr 25, 2017 at 10:31 AM, Bruce Momjian <br...@
In fact I wonder if it's necessary to list
> this one at all.
Yes, I removed it. We can always re-add it later.
>
> Increase the maximum configurable WAL size to 1
> gigabyte (Beena Emerson)
>
> "WAL segment size" perhaps, and note that t
On Fri, May 5, 2017 at 02:28:50PM +0200, Petr Jelinek wrote:
> On 05/05/17 02:46, Bruce Momjian wrote:
> > I am getting tired of saying this. When I am writing the release notes,
> > I am trying to figure out how it affects our shipped code, and the only
> > "decoding&q
Uses page-based mechanism to ensure we’re using the correct
timeline.
Tests are included to exercise the functionality using a cold
disk-level copy
of the master that's started up as a replica with slots intact, but
the
intended use of the functionality is w
e more powerful in PG 11. Any
better wording?
I will work on the other items you posted shortly.
--
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. +
+
.
OK, added, thanks:
+
+ Improve accuracy in determining if a BRIN index scan
+ is beneficial (David Rowley, Emre Hasegeli)
+
+
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB
nes, would have a visible performance change. It is
difficult to determine this from the release notes, which is why I
always need feedback on these items.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB ht
On Mon, May 1, 2017 at 08:02:46AM -0400, Robert Haas wrote:
> On Tue, Apr 25, 2017 at 11:01 AM, Bruce Momjian <br...@momjian.us> wrote:
> >> Or the ability of logical decoding to follow timeline switches.
> >
> > I didn't think logical decoding was really more tha
On Fri, Apr 28, 2017 at 01:12:34PM +0900, Masahiko Sawada wrote:
> On Tue, Apr 25, 2017 at 10:31 AM, Bruce Momjian <br...@momjian.us> wrote:
> > I have committed the first draft of the Postgres 10 release notes. They
> > are current as of two days ago, and I will keep
On Thu, Apr 27, 2017 at 04:05:09PM +0100, Dagfinn Ilmari Mannsåker wrote:
> Bruce Momjian <br...@momjian.us> writes:
>
> > I have committed the first draft of the Postgres 10 release notes. They
> > are current as of two days ago, and I will keep them current. Please
>
> The same with v10 leads instead to
> select '1st buffer'
>
> I'm not sure whether it's above the level of detail worth being mentioned
> in the release notes.
Wow, I am not sure how to even explain that. ;-) Let's see if we get
any user feedback on the change.
--
Bruce
s
> itself.
>
> I'm not sure how this should appear in the release notes. Maybe not at all,
> associated to the feature in which the behavioral change was introduced...
Agreed, I removed the item and moved those commits to the \if item.
--
Bruce Momjian <br...@momjian.us>
On Thu, Apr 27, 2017 at 10:21:44AM +0500, Andrew Borodin wrote:
> Hi, Bruce!
>
> 2017-04-25 6:31 GMT+05:00 Bruce Momjian <br...@momjian.us>:
> > The only unusual thing is that this release has ~180 items while most
> > recent release have had ~220. The pattern I see th
;Add write-ahead logging support to hash indexes", so it seems
> inappropriate to add them here. We can add it along with below item:
>
>
>
> Add write-ahead logging support to hash indexes (Amit Kapila)
>
OK, commits moved.
--
Bruce Momjian <
; > 2017-02-14 [5e6d8d2bb] Allow parallel workers to execute subplans.
> >
> > Allow non-correlated subqueries to be run in parallel (Amit Kapila)
> >
>
> Looks good to me.
OK, added.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
On Wed, Apr 26, 2017 at 11:41:51PM +0200, Petr Jelinek wrote:
> On 26/04/17 18:59, Bruce Momjian wrote:
> > I tried setting up logical replication on the same server between two
> > different databases, and got, from database test:
> >
> > test=> CREATE
pected? I can get it working from two different clusters.
--
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 inscriptio
queries can be run in parallel. Yes, that is
something we should have in the release notes. How is this?
Author: Robert Haas <rh...@postgresql.org>
2017-02-14 [5e6d8d2bb] Allow parallel workers to execute subplans.
Allow non-correlated subqueries to be run in parallel (
ill fix it as a stabilization work.
We did work in Postgres 10 to make replication simpler with better
defaults. This would be part of that improvement.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB http://enterpris
cee2293c5e4) which has an independent
> value.
Oh, yes, added. I think in a quick look I saw Rafia Sabih as the same
as Rahila Syed and thought the name was already listed. Sorry to both of
them.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB
On Tue, Apr 25, 2017 at 09:56:58PM -0400, Bruce Momjian wrote:
> > SCRAM-SHA-256 improves deficiencies of MD5 password hashing by
> > preventing any kind of pass-the-hash vulnerabilities, where a user
> > would be able to connect to a PostgreSQL instance by just knowing the
>
On Tue, Apr 25, 2017 at 07:17:20PM -0700, Andres Freund wrote:
> On 2017-04-25 22:13:00 -0400, Bruce Momjian wrote:
> > On Tue, Apr 25, 2017 at 06:40:08PM -0700, Andres Freund wrote:
> > > On 2017-04-25 21:19:41 -0400, Bruce Momjian wrote:
> > > > On Tue, Apr 25,
On Tue, Apr 25, 2017 at 06:40:08PM -0700, Andres Freund wrote:
> On 2017-04-25 21:19:41 -0400, Bruce Momjian wrote:
> > On Tue, Apr 25, 2017 at 06:51:47AM +0200, Petr Jelinek wrote:
> > > Or the ability of logical decoding to follow timeline switches.
> >
> > When y
On Wed, Apr 26, 2017 at 11:06:03AM +0900, Michael Paquier wrote:
> On Wed, Apr 26, 2017 at 10:56 AM, Bruce Momjian <br...@momjian.us> wrote:
> > First, I don't think RFC references belong in the release notes, let
> > alone RFC links.
> >
> > Second, there see
On Wed, Apr 26, 2017 at 09:02:51AM +0900, Michael Paquier wrote:
> On Wed, Apr 26, 2017 at 12:20 AM, Bruce Momjian <br...@momjian.us> wrote:
> > On Tue, Apr 25, 2017 at 02:39:40PM +0900, Michael Paquier wrote:
> >>
> >> Add SCRAM-SHA-256
> >> support for
When you say "logical decoding", you don't mean contrib/test_decoding?
Do you mean the WAL logical stream now has timeline information and 3rd
party software should know about that?
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB
ess for every host name.
Patch by me. Victor Wagner wrote an earlier patch for this feature,
which I read, but I didn't use any of his code. Review by Mithun
Cy.
Was it wrong?
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB
display_ed_ in other cases."
OK, got it:
By default planning and execution time are display by
EXPLAIN ANALYZE and are not display in other cases.
The new EXPLAIN option SUMMARY allows
explicit control of this.
--
Bruce Momjian <br...@momjian.us>http://m
On Tue, Apr 25, 2017 at 08:12:05PM +0200, Petr Jelinek wrote:
> On 25/04/17 17:01, Bruce Momjian wrote:
> >
> >> I also wonder if ability to run SQL queries on walsender connected to a
> >> database is worth mentioning (replication=database kind of connecti
On Tue, Apr 25, 2017 at 01:44:09PM -0400, Tom Lane wrote:
> Bruce Momjian <br...@momjian.us> writes:
> > On Tue, Apr 25, 2017 at 10:00:52AM -0700, Andres Freund wrote:
> >> at this point, you can see, we've squarely left O(N) country, and
> >> entered the vast O(N^
On Tue, Apr 25, 2017 at 10:37:48AM -0700, Andres Freund wrote:
> On 2017-04-25 13:11:32 -0400, Bruce Momjian wrote:
> > I don't think this warrants inclusion in the release notes for reasons
> > already discussed. The vacuum truncation operation is a rare one and
> > an
hand I have a responsibility to be consistent what what they have
wanted in the past. I am also open to reviewing how we filter things
compared other projects.
On a larger note, not being in the release notes doesn't mean it isn't
important, but rather, that is isn't a change users need to know
creation speed in sessions that reference many
relations (Aleksander Alekseev)
--
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. +
+
On Tue, Apr 25, 2017 at 01:06:05PM -0400, Tels wrote:
> Moin,
>
> On Mon, April 24, 2017 9:31 pm, Bruce Momjian wrote:
> > I have committed the first draft of the Postgres 10 release notes. They
> > are current as of two days ago, and I will keep them current. Please
>
kydo1tguh791z6py...@mail.gmail.com
I don't think this warrants inclusion in the release notes for reasons
already discussed. The vacuum truncation operation is a rare one and
an implementation detail.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
EnterpriseDB
On Tue, Apr 25, 2017 at 11:20:46AM -0400, Bruce Momjian wrote:
> Oh, I made a mistake there, fixed.
>
> >
> >
> >
> > New major version numbering (Peter Eisentraut, Tom Lane)
> >
> >
> > Major versions will now increase just the first n
Paquier.
Oh, I made a mistake there, fixed.
>
>
>
> New major version numbering (Peter Eisentraut, Tom Lane)
>
>
> Major versions will now increase just the first number, and minor
> releases will increase just the second number. A third number will no
> longer be use
On Tue, Apr 25, 2017 at 03:15:45PM +0200, Félix GERZAGUET wrote:
> Hello Bruce,
>
> On Tue, Apr 25, 2017 at 3:31 AM, Bruce Momjian <br...@momjian.us> wrote:
>
> I have committed the first draft of the Postgres 10 release notes. They
> are current as of two days a
> execution time (Stephen Frost)
>
> By default planning and execution is display by EXPLAIN ANALYZE and
> not display in other cases. The new EXPLAIN option SUMMARY allows
> explicit control of this.
Oh, I missed that 'Author' line, fixed.
--
Bruce Momjian <br...@momjian.
On Tue, Apr 25, 2017 at 06:51:47AM +0200, Petr Jelinek wrote:
> On 25/04/17 03:31, Bruce Momjian wrote:
> > I have committed the first draft of the Postgres 10 release notes. They
> > are current as of two days ago, and I will keep them current. Please
> > give me
On Tue, Apr 25, 2017 at 01:10:35PM +0900, Amit Langote wrote:
> On 2017/04/25 10:31, Bruce Momjian wrote:
> > I have committed the first draft of the Postgres 10 release notes. They
> > are current as of two days ago, and I will keep them current. Please
> > give me
On Tue, Apr 25, 2017 at 04:03:53PM +1200, David Rowley wrote:
> ..On 25 April 2017 at 13:31, Bruce Momjian <br...@momjian.us> wrote:
> > The only unusual thing is that this release has ~180 items while most
> > recent release have had ~220. The pattern I see that the
rror. Unfortunately, they are not, so we would have to find a way to
pass those comments into the HTML.
--
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. +
On Tue, Apr 25, 2017 at 09:38:55AM +0530, Rafia Sabih wrote:
> On Tue, Apr 25, 2017 at 9:15 AM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> > Andres Freund <and...@anarazel.de> writes:
> >> On 2017-04-24 23:37:42 -0400, Bruce Momjian wrote:
> >>> I remember see
On Mon, Apr 24, 2017 at 08:52:05PM -0700, Andres Freund wrote:
> On 2017-04-24 23:45:06 -0400, Tom Lane wrote:
> > Andres Freund <and...@anarazel.de> writes:
> > > On 2017-04-24 23:37:42 -0400, Bruce Momjian wrote:
> > >> I remember seeing those and tho
On Mon, Apr 24, 2017 at 08:39:59PM -0700, Andres Freund wrote:
> On 2017-04-24 23:37:42 -0400, Bruce Momjian wrote:
> > I remember seeing those and those are normally details I do not put in
> > the release notes as there isn't a clear user experience change except
> > "
On Tue, Apr 25, 2017 at 09:00:45AM +0530, Amit Kapila wrote:
> On Tue, Apr 25, 2017 at 8:35 AM, Bruce Momjian <br...@momjian.us> wrote:
> > On Tue, Apr 25, 2017 at 08:30:50AM +0530, Amit Kapila wrote:
> >> On Tue, Apr 25, 2017 at 7:01 AM, Bruce Momjian <br...@momji
On Mon, Apr 24, 2017 at 08:36:00PM -0700, Andres Freund wrote:
> On 2017-04-24 21:31:44 -0400, Bruce Momjian wrote:
> > I have committed the first draft of the Postgres 10 release notes. They
> > are current as of two days ago, and I will keep them current. Please
> > giv
On Mon, Apr 24, 2017 at 11:05:41PM -0400, Bruce Momjian wrote:
> > I think the above commit needs a separate mention, as this is a really
> > huge step forward to control the size of hash indexes.
>
> Yes, it is unfotunate that the item is in the incompatibility item. I
&g
On Tue, Apr 25, 2017 at 08:36:38AM +0530, Amit Kapila wrote:
> On Tue, Apr 25, 2017 at 8:30 AM, Amit Kapila <amit.kapil...@gmail.com> wrote:
> > On Tue, Apr 25, 2017 at 7:01 AM, Bruce Momjian <br...@momjian.us> wrote:
> >> I have committed the first draft of
On Tue, Apr 25, 2017 at 08:30:50AM +0530, Amit Kapila wrote:
> On Tue, Apr 25, 2017 at 7:01 AM, Bruce Momjian <br...@momjian.us> wrote:
> > I have committed the first draft of the Postgres 10 release notes. They
> > are current as of two days ago, and I will keep them current
ues for validity
> (Artur Zakirov)
>
> "check" is repeated.
>
>
> (5)
> Use POSIX semaphores rather than SysV semaphores on Linux and FreeBSD (Tom
> Lane)
> This avoids some limits on SysV semaphores usage.
>
> These two lines are put in two different ite
On Tue, Apr 25, 2017 at 03:45:52AM +0200, Andreas Karlsson wrote:
> On 04/25/2017 03:31 AM, Bruce Momjian wrote:
> >I have committed the first draft of the Postgres 10 release notes. They
> >are current as of two days ago, and I will keep them current. Please
> >give me
that there are more
large features in this release than previous ones.
--
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
On Sun, Apr 23, 2017 at 10:01:16AM -0400, Bruce Momjian wrote:
> On Sun, Apr 23, 2017 at 11:44:12AM +0100, Simon Riggs wrote:
> > For us "functional dependency" would sound like something to do with
> > functions (e.g. CREATE FUNCTION), so just "dependency" ap
istics for dependency stored, hence
> "dependencies". I don't like it, but its the best term I can see at
> present.
OK, thank you for the reply, and I am sorry I forgot the previous
discussion. I just wanted to re-check we had research this. Thanks.
--
Bruce Momjian <br.
In looking at the new multi-column statistics "dependency" option in
Postgres 10, I am quite confused by the term "dependency". Wouldn't
"correlation" be clearer and less confusing as "column dependency"
already means something else.
--
Bruce
go forward and I will work on the intermediate certificate issue
in a few months.
--
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. +
+
On Mon, Apr 17, 2017 at 03:43:09PM -0400, Tom Lane wrote:
> Bruce Momjian <br...@momjian.us> writes:
> > I think the reason we have those cumbersome instructions is that there
> > is no way to create a non-expireable certificate using simpler
> > instructions.
t there
is no way to create a non-expireable certificate using simpler
instructions.
I would like to revisit these instructions, as well as document how to
create intermediate certificates. I have scripts that do that.
--
Bruce Momjian <br...@momjian.us>http://momjian.us
Enterpr
nobody
> has a rule to follow about which way to name new exposed references to
> the concept, and that's simply bad.
>
> It's possible that we should say that backwards compatibility outweighs
> consistency and therefore it's too late to change these names. But
> I think your
m/postgres/pgweb/commit/c513457da76a4d864f706c21312d3def1fc8f8c8
I think the only open issue is the JavaScript CSS font fix that has a
posted patch here:
https://www.postgresql.org/message-id/20170408015201.ga18...@momjian.us
--
Bruce Momjian <br...@momjian.us>http://
ow-level tool where people have to figure more things
> out themselves.
Well, pg_upgrade creates ./analyze_new_cluster.sh, but that just
contains:
"/u/pgsql/bin/vacuumdb" --all --analyze-in-stages
Seems like we should just get rid of ./analyze_new_cluster.sh and tell
the user
101 - 200 of 16619 matches
Mail list logo
