g that isn't shipped by us? I thought WAL support was something
that prevented external indexing solutions from working.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you w
wer the questions you
asked above.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription +
--
Sent via pgsql-hackers ma
I think we are basically making that attempt now.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription +
--
Sent via pgsql-hack
s you
just need to create infrastructure and see how well it solves problems.
The weird thing is that if you do implement an ill-defined feature,
there really isn't much huge positive feedback --- people just use the
feature, and the complaints stop.
--
Bruce Momjian ht
h to meet some random person's particular use case.
> Ah well.
As they say, if this was easy, everyone would be doing it. ;-)
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so yo
urse, there will be a lot
> to
> learn, but it will be much easier if XTM will exists not as separate patch,
> which is really small.
I think everyone agrees we want a global transaction manager of some
type. I think choosing the one we want is the problem as there are
several possible di
. it would be nice of one of these was more active in the
second half of the checkpoint period. I assume that is what is being
discussed here.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As
4096 Jan 17 12:19 data/
^^^group
I assume we don't want to change that.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription
On Sun, Jan 17, 2016 at 01:49:19PM -0500, Stephen Frost wrote:
> * Bruce Momjian (br...@momjian.us) wrote:
> > > pgbackrest:
> > >
> > > To run pgbackrest as a non-superuser and not the 'postgres' system
> > > user, grant the pg_backup role to
ed new
ones.
That all seems very straight-forward to me.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription +
--
Sent via
ange of values
> for a range of heap pages.
FYI, that TODO entry was removed since July 9, probably as part of my
9.5 cleanup.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be
hen granting
permissions on that function to the backup role. This is another
example where different backup tools need different permissions.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, s
gt; sense is to add additional functions in some cases. In particular, we
> will need alternate versions of pg_terminate_backend and
> pg_cancel_backend. One thought I had was to make that
Like these? Could we define own-user-type rights?
--
Bruce Momjian http://momjian.us
Enter
BwRvH4cE-nN9y5gj8ZLCO7KMrlvYg/view
>
> > Fuzzer:
> > https://docs.google.com/presentation/d/12Dd9Bhcugkdi2w0ye4T1fy9ccjconJEz9cNthdeyH7k/view
>
> Very cool, thanks!
No, you need to see the video! It was amazing. I couldn't believe what
I was hearing. I was like &qu
ess to the data directory, I
> would expect every backup soltuion to view that as a feature which they
> want to support, as there are environments which will find it desirable,
> at a minimum, and even some which will require it.
pg_dump doesn't need to read the PGDATA directory,
erally consider that to be the case,
> myself, but it seems others do...).
I think the source of that is that many people have asked for
backup-only uses, and I thought running pg_dump or pg_dumpall was one of
those cases.
--
Bruce Momjian http://momjian.us
EnterpriseDB
o.id = la.obj_id
AND o.owner = la.user_id,
mime m,
users uc,
users uo
WHERE (
s.mime_id = 904
OR s.mime_id = 908 )
AND m.mime_id = o.mime_id
AND o.owner = uo.user_id
AND o.creator = uc.user_id
can now see storage latency that is practically
> on-par with things like lock acquisition[1].
How is this different from Fusion I/O devices, which have been around
for years?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As y
source installation into
> one session.
The fix for that would be for pg_upgrade to change
check_loadable_libraries() to start a new session for each LOAD command.
Would you like that done?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprise
e the plan if the selectivity estimates are
similar. Isn't parameter selectivity the only thing that distinguishes
on plan with parameter from another?
Checking selectivity estimates must be cheaper than replanning. This
could be done at the second use of the prepared plan, and maybe for a
On Mon, Jan 18, 2016 at 02:14:11PM -0500, Tom Lane wrote:
> Bruce Momjian writes:
> > I never understood why we don't just keep the selectivity estimates of
> > previous plans and just reuse the plan if the selectivity estimates are
> > similar. Isn't parameter
; _("off"));
> > ! printf(_("Latest checkpoint's NextXID: %u:%u\n"),
> > This should be definitely a separate patch.
>
> Ok. Notwithstanding Simon's reply, there seems to be consensus that this
> is the way to go. Will commit it
fOn Mon, Jan 18, 2016 at 01:54:02PM -0800, Joe Conway wrote:
> On 01/18/2016 01:47 PM, Bruce Momjian wrote:
> > On Sun, Jan 17, 2016 at 02:24:46PM -0800, Joe Conway wrote:
> >> On 01/16/2016 06:02 AM, Michael Paquier wrote:
> >>> On Wed, Dec 30, 2015 at 9:08 AM, Joe C
On Mon, Jan 18, 2016 at 01:10:05PM -0500, Tom Lane wrote:
> Bruce Momjian writes:
> > On Mon, Jan 11, 2016 at 10:44:42AM -0500, Tom Lane wrote:
> >> But it gets worse: a report today in pgsql-general points out that
> >> even if you have the two languages in
On Mon, Jan 18, 2016 at 07:50:12PM -0500, Bruce Momjian wrote:
> > >>>> 1) Change NextXID output format from "%u/%u" to "%u:%u"
> > >>>>(see recent hackers thread)
> > >>>
clude/ we had better change that as well, and it makes the
> code cleaner.
I have applied this patch all the way back to 9.1. This means PL/Java
can be cleanly built via MSVC on Windows for all installs after the next
set of minor releases.
--
Bruce Momjian http://momjian.us
Ente
ooks more like the 8.X series of release
dates. Everyone might be fine with that, but we had better be prepared
for November-February major release dates going forward.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are,
On Wed, Jan 20, 2016 at 04:48:16PM +0100, Andres Freund wrote:
> On 2016-01-20 10:40:14 -0500, Bruce Momjian wrote:
> > We have gotten off of that cycle in the last two major releases, and
> > this isn't going to improve as long as we have commitfests starting
> > after
stain five commitfests and stay on time
--- we need to go back to four, which I think is what we used to do. We
twiddled our thumbs back in the September-release years too, but had
consistency because twiddling was built into the schedule.
--
Bruce Momjian http://momjian.us
Enterpris
format from STS but not previous LTS.
> This allows two LTS versions per 5 year support cycle
I just don't buy the Ubuntu release model for our database. Ubuntu is
trying to balance hot features vs stability, while we are really focused
on stability, similar to Debian.
--
Br
hat* would be manifestly unfair.
Unfair or not, that is probably the effect. I can also see people
publishing git trees to avoid this roadblock.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am,
t; >solution seems to be explicit schema for statistics.
>
> That solution seems good to me.
>
> (with apologies for not having looked at the rest of this much at all)
Woh, this will be an optimizer game-changer, from the user perspective!
--
Bruce Momjian http://
ly about for us anyway)
> * Decreased concerns about upgrades and ability to extend upgrade status.
I can see LTS working for plugin change, but not server binary changes.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+
ue, and people are not improving the TODO list
situation, how likely will a bug tracker be at improving or
deteriorating the situation?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I a
; with 9.3. It might be a good idea to formally state what those lessons
> are.
I do think that is effectively a lesson we learned, wrong or not.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was
we could do integration and get to beta in May --- at least we
have never been able to do that.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription
re to expand that to
cover reviewers, we would then be overburdinging that system and we
would probably end up removing all names from the release notes.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. A
On Wed, Jan 20, 2016 at 05:56:27PM -0500, Tom Lane wrote:
> Bruce Momjian writes:
> > On Wed, Jan 20, 2016 at 01:59:59PM -0800, Peter Geoghegan wrote:
> >> I think that we've learned some lessons from the problems with 9.3. I
> >> don't think that one of
On Thu, Jan 21, 2016 at 12:05:19AM +0100, Andres Freund wrote:
> On 2016-01-20 18:02:20 -0500, Bruce Momjian wrote:
> > The two sobering blockers I can remember were multi-xact (9.3) and JSONB
> > compression (9.4).
>
> I don't see how those compare. The multixact
--
Report by
Patch by
Reviewed by
Backpatch through
The dashed lines are used to specify a target length for the summary
line and are automatically removed before the commit message is posted.
--
Bruce Momjian http
On Thu, Jan 28, 2016 at 03:52:00AM -0500, Bruce Momjian wrote:
> There has been a request in the FOSDEM developers meeting that
> committers use a more consistent format for commit messages. This is
> the format I use:
Here is an updated version that includes a potential b
Reviewed-by:
Backpatch through:
I had to make up "Patch-by:" as it wasn't listed.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so yo
ated based on those suggestions:
-- email subject limit -
-- gitweb summary limit --
Reported-by:
Bug:
Author:
Reviewed-by:
Tested-by:
Backpatch-through
we could find another
> way to phrase that, like "Design-suggestions-by" or maybe a more
> general "Suggestions-by".
I wasn't sure if "User-Interface-Bikeshedded-By" related to the patch,
or to the discussion of labels for the commit messages.
--
Bruce Momj
lar issue with it, but would like whatever
> template is decided upon to be included in our git repo and then we
> should be able to make it the template that's opened up when people go
> to commit pretty easily.
OK, but keep in mind whatever script committers user should remove tags
t
k lines:
sed -e :a -e '/./,$!d;/^\n*$/{$d;N;};/\n$/ba'
and this removes adjacent blank lines:
cat --squeeze-blank
I can publish my script at the appropriate time.
--
Bruce Momjian http://momjian.us
EnterpriseDB http:/
is the limit on subject size. Sometimes it's very
> difficult to be sufficiently communicative in, say, 50 characters.
Agreed, but that is a gitweb limit we can't control, I think.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enter
ontroldata, so you would be adding a dependency in ordering of the
> pg_controldata entries.
By testing for '906', you prevent users from using pg_upgrade to go from
one catalog version of 9.6 to a later one. Few people may want to do
it, but it should work.
--
Bruce Momjian
On Thu, Feb 11, 2016 at 07:18:46PM -0500, Bruce Momjian wrote:
> No, that is not an improvement --- see my previous comment:
>
> > We could get more sophisticated by checking the catalog version number
> > where the format was changed, but that doesn't seem worth it, an
uster data
directory inside the old data directory, only a check for tablespace
directories in the old cluster. (I never anticipated someone would do
this.)
The attached patch adds the proper check. This should be backpatched to
all supported Postgres versions.
--
Bruce Momjian http://
pre-9.6 to 9.6+, so why not just hard-code in the functions we need. We
can remove it once 9.5 is end-of-life.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman gra
ommended a best way.
So, the question is, do we feel that PgLogical is best and recommended
way to do logical replication. If it is, then having it in core makes
sense.
--
Bruce Momjian http://momjian.us
EnterpriseDB http
for every upgrade from
> > pre-9.6 to 9.6+, so why not just hard-code in the functions we need. We
> > can remove it once 9.5 is end-of-life.
> >
>
> Hm, we should rather remove the source code around PAGE_CONVERSION and
> page.c at 9.6?
Yes. I can do it if you
he commit that should have been listed here, likely.
>
> Are you willing to fix it?
Fixed and patched back to 9.5.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will b
On Tue, Feb 16, 2016 at 03:57:01PM -0300, Alvaro Herrera wrote:
> Masahiko Sawada wrote:
> > On Wed, Feb 17, 2016 at 12:02 AM, Bruce Momjian wrote:
> > > On Tue, Feb 16, 2016 at 11:56:25PM +0900, Masahiko Sawada wrote:
> > >> > I agreed on ripping out the conve
diting code seems very similar to how to handle the logical
replication of DDL commands. First, have we looked into hooking
auditing into scanning logical replication contents, and second, how are
we handling the logical replication of DDL and could we use the same
approach for auditing?
--
On Wed, Feb 17, 2016 at 01:59:09PM +0530, Robert Haas wrote:
> On Wed, Feb 17, 2016 at 5:20 AM, Bruce Momjian wrote:
> > On Fri, Feb 5, 2016 at 01:16:25PM -0500, Stephen Frost wrote:
> >> Looking at pgaudit and the other approaches to auditing which have been
> >>
her to
> trust the specific group, but I don't think there's any practical
> way to do that. System conventions vary too much.
Should we have a GUC to control the group permissions restriction? I
can certainly see value in allowing for group access to the certificate.
--
Bruce Momj
On Mon, Feb 15, 2016 at 06:32:06PM +0100, Magnus Hagander wrote:
>
>
> On Mon, Feb 15, 2016 at 6:29 PM, Bruce Momjian wrote:
>
> Someone on IRC reported that if they had run the pg_upgrade-created
> delete_old_cluster.sh shell script it would have deleted their old _a
;t need to read the WAL to do the auditing, but the same
facility could be used for both, e.g. output some JSON standard format
that both logical replication and auditing could understand.
The bottom line is we need to crack the record-DDL nut somehow, and at
least in this case, we h
On Fri, Feb 19, 2016 at 12:54:17PM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > Understood. My point is that there is a short list of read events, and
> > many DDL events. We have already hesitated to record DDL changes for
> > logical replication
On Fri, Feb 19, 2016 at 11:20:13AM -0500, David Steele wrote:
> On 2/19/16 10:54 AM, Alvaro Herrera wrote:
> > Bruce Momjian wrote:
> >
> >> Understood. My point is that there is a short list of read events, and
> >> many DDL events. We have already he
On Fri, Feb 19, 2016 at 08:20:31AM -0800, Andres Freund wrote:
> On 2016-02-19 10:14:47 -0500, Bruce Momjian wrote:
> > We have already hesitated to record DDL changes for
> > logical replication because of the code size, maintenance overhead, and
> > testing required.
&
a.
> >
> > Agreed.
>
> +1. I think this is clearly a back-patchable fix.
Fix applied to head and 9.5.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman
with our current
FDW sharding approach.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription +
--
Sent via pgsql-hacke
On Tue, Feb 23, 2016 at 09:54:46AM -0700, David G. Johnston wrote:
> On Tue, Feb 23, 2016 at 9:43 AM, Bruce Momjian wrote:
>
> 4. Cross-node read-write queries:
>
> This will require a global snapshot manager and global snapshot manager.
>
>
> Probably m
On Thu, Aug 7, 2014 at 01:26:24PM +0900, Fujii Masao wrote:
> On Thu, Aug 7, 2014 at 2:17 AM, Bruce Momjian wrote:
> >
> > Seems we still have not addressed this.
>
> Thanks for the reminder :) I'm not sure if I have time to work on this
> for a while. If anyone
On Wed, Feb 24, 2016 at 01:08:29AM +, Simon Riggs wrote:
> On 23 February 2016 at 16:43, Bruce Momjian wrote:
>
> There was discussion at the FOSDEM/PGDay Developer Meeting
> (https://wiki.postgresql.org/wiki/FOSDEM/PGDay_2016_Developer_Meeting)
> about sharding
only existing approach for
built-in sharding though. The forks of Postgres doing sharding are,
just that, forks and just Postgres community ecosystem projects. (Yes,
they are open source.) If the forks were community-chosen plans we
hopefully would not have 5+ of them. If FDW works, it ha
sting soltion, which then doesn't need to be
maintained anymore, or used by existing solutions.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription
> product providing functionality similar to Oracle RAC or MySQL
> Gallera. It is yet another direction of cluster development for
> PostgreSQL. Let's be more open and flexible.
Yes, I listed only the workloads I could think of. It would be helpful
to list more workloads and start to decide wha
On Wed, Feb 24, 2016 at 09:34:37AM -0500, Bruce Momjian wrote:
> > I have nothing against particular FDW advances. However, it's unclear for me
> > that FDW should be the only sharding approach.
> > It's unproven that FDW can do work that Postgres XC/XL does. With
On Wed, Feb 24, 2016 at 01:02:21PM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > On Wed, Feb 24, 2016 at 01:08:29AM +, Simon Riggs wrote:
>
> > > It's never been our policy to try to include major projects in single code
> > > drops. Any move of XL
hat is cool. Can anyone suggest which commit improved this?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription +
--
Sent v
On Thu, Feb 25, 2016 at 12:50:06PM +1300, Thomas Munro wrote:
> On Thu, Feb 25, 2016 at 12:26 PM, Bruce Momjian wrote:
> > On Thu, Feb 25, 2016 at 10:06:34AM +1100, James Sewell wrote:
> >> Now when I run the following SQL (multiple times to allow for getting
> >> eve
nd has moved to PostgreSQL
> license exactly to allow Postgres core to reuse it later on if needed.
Ah, yes, I remember that now. Thanks.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, s
ro have *two* GTMs instead of a single one?
I think the issue is that a GTM that works for a low-latency network
doesn't work well for a high-latency network, so the high-latency GTM
has fewer features and guarantees.
--
Bruce Momjian http://momjian.us
EnterpriseDB
hard to do
> because typical SQL doesn't record what concurrent transactions
> committed before a new statement's transaction snapshot is taken, and
> doesn't record lock order for row updates blocked by concurrent activity
> --- both of which affect the final result f
resented in PG 10 as:
local "Test" all trust
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ A
On Thu, Aug 18, 2016 at 02:06:39PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > I was looking at this TODO item from 2009:
> > https://www.postgresql.org/message-id/4AA7B197.70002%40usit.uio.no
> > I have implemented this in the attached patch. It does two things:
On Thu, Aug 18, 2016 at 03:01:48PM -0400, Peter Eisentraut wrote:
> On 8/18/16 1:59 PM, Bruce Momjian wrote:
> > o compares words in columns that can only support keywords as
> > case-insensitive, double-quoted or not
> >
> > o compares words in columns that c
/Todo
--
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 +
--
Sent via pgsql-hackers mailing list (pgsql-hackers
Someone reported that a replication slot that existed at the time a base
backup was done on the master was copied to the standby. Because they
didn't realize it, their WAL was not being recycled on the standby.
Is that possible? Is it a known behavior? I don't see it documented.
-
On Sat, Aug 20, 2016 at 01:43:42PM +0900, Michael Paquier wrote:
> On Sat, Aug 20, 2016 at 1:39 PM, Bruce Momjian wrote:
> > Someone reported that a replication slot that existed at the time a base
> > backup was done on the master was copied to the standby. Because they
> &
On Thu, Aug 18, 2016 at 04:49:04PM -0400, Bruce Momjian wrote:
> On Thu, Aug 18, 2016 at 03:01:48PM -0400, Peter Eisentraut wrote:
> > On 8/18/16 1:59 PM, Bruce Momjian wrote:
> > > o compares words in columns that can only support keywords as
> > > case-insens
ches so we can backpatch things. The ideal time would probably
be right after we have done minor releases. The problem is that this is
going to break queued-up patches, so maybe it has to be done right
before 10.0 beta, and again, to all back branches too.
--
Bruce Momjian
On Fri, Aug 19, 2016 at 09:22:32AM -0700, Jeff Janes wrote:
> On Sat, Jul 30, 2016 at 11:18 AM, Bruce Momjian wrote:
>
> On Fri, Jul 29, 2016 at 11:27:06AM -0400, Peter Eisentraut wrote:
> > On 7/29/16 11:13 AM, Bruce Momjian wrote:
> > > Yes, I am thinking
after experimenting with this, I did not find any way to get perltidy
> to overwrite the original files without making a backup file.
Yep, that's why --backup-and-modify-in-place had to be used. I have a
local script to remove file with specified extentions, but didn
On Tue, Aug 23, 2016 at 01:30:29PM -0400, Robert Haas wrote:
> On Fri, Jul 29, 2016 at 8:18 PM, Bruce Momjian wrote:
> > and the units were copied when pg_size_pretty() was implemented. These
> > units are based on the International System of Units (SI)/metric.
> > Howe
On Tue, Aug 23, 2016 at 01:45:44PM -0400, Robert Haas wrote:
> On Tue, Aug 23, 2016 at 1:43 PM, Bruce Momjian wrote:
> > On Tue, Aug 23, 2016 at 01:30:29PM -0400, Robert Haas wrote:
> >> On Fri, Jul 29, 2016 at 8:18 PM, Bruce Momjian wrote:
> >> > and the units w
On Tue, Aug 23, 2016 at 01:53:25PM -0400, Robert Haas wrote:
> On Tue, Aug 23, 2016 at 1:47 PM, Bruce Momjian wrote:
> >> I have already read the entire thread, and replied only after reading
> >> all messages.
> >
> > Well, what are you replying to then?
>
&
On Tue, Aug 23, 2016 at 02:31:26PM -0400, Robert Haas wrote:
> On Tue, Aug 23, 2016 at 1:57 PM, Bruce Momjian wrote:
> > That's why I was asking you to comment on the final patch, which I am
> > planning to apply to PG 10 soon.
>
> Oh, OK. I didn't understand th
On Tue, Aug 23, 2016 at 11:35:35AM -0700, Andres Freund wrote:
> On 2016-08-23 14:33:15 -0400, Bruce Momjian wrote:
> > On Tue, Aug 23, 2016 at 02:31:26PM -0400, Robert Haas wrote:
> > > On Tue, Aug 23, 2016 at 1:57 PM, Bruce Momjian wrote:
> > > > That's why
ndows]
> #clients onoff
> 12 29793 38169
> 24 31587 87237
> 48 32588 83335
> 96 34261 67668
This ranges from a 28% to a 97% speed improvement on Windows! Those are
not typos! This is a game-changer for use of Postgres on Windows for
certain workloads!
--
On Tue, Aug 23, 2016 at 01:58:02PM -0700, Peter Geoghegan wrote:
> On Tue, Aug 23, 2016 at 1:44 PM, Bruce Momjian wrote:
> >> [Windows]
> >> #clients onoff
> >> 12 29793 38169
> >> 24 31587 87237
> >> 48 32588 83335
> >> 9
ime to rename pg_xlog and pg_clog directories 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 +
--
Sent via pgsql-h
rformance hits in switching WAL files so they might
be tempted to set very high segment sizes in inappropriate cases.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+
gt;
> (This is all about XLOG_SEG_SIZE; I presume XLOG_BLCKSZ can stay as it
> is, right?)
I think having WAL use variable length files would add complexity for
recycling WAL files.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterpris
t; That would not be complicated to fix for any tool maintainers.
I agree on a hard break, unless we get pushback from users, and even
then, they can create the symlinks themselves.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
business. Pushing them without any testing
> is close to irresponsible.
Not being around to fix the breakage after the commit isn't great
either.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so onc
1 - 100 of 17339 matches
Mail list logo
