, that suggestion of 400 seems confirmed to
be sane now to me.
--
* Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
different between that system and the others.
--
* Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
been a regular application
technique for at least two years now, since
http://www.varlena.com/GeneralBits/120.php popularized it.
--
* Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
and
run this again, it would be good to let pgbench run for a lot longer than
1 minute, to see if the results show some more significant difference.
With this few TPS, it would be nice to let that run for 30 minutes or more
if you can find some time to schedule that.
--
* Greg Smith [EMAIL
Greg's Law of DBAs: the larger and more critical a
database is, the more likely it is to attract a clueful DBA to take care
of it.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
entry on saving plans to tables in
PostgreSQL, unfortunately the Planet PostgreSQL outage seems to have eaten
it.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
changes.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Fri, 5 Dec 2008, Greg Smith wrote:
If it is needed, I'd suggest you'd get a warmer reception here submitting two
diffs, one that just did the renaming and a second that actually had the
functional bits in it.
You can just ignore this late night bit of idiocy, or mock me for it as
you see
it too,
particularly for a patch of this size.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Looks like Robert accidentally answered my question about what version his
results were from off-list. Here's his update:
---
Unfortunately it was 8.2.9, as I realized halfway into the run. Here are
the results from a CVS HEAD checkout last night.
*** Query planning times
q1 (the complex
then and see how I did implementing your
suggestions, that would be great.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
posted so far is now listed
under Development Projects on the wiki:
http://wiki.postgresql.org/wiki/C%2B%2B_Compatibility
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
of
per-table catalog data being proposed to push into 8.4 for making future
upgrades easier, this seems like a possible candidate for something to
make space for there. As I just came to appreciate the problem I'm not
sure about that.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com
for the
first release.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
of what comes out of initdb already; I'm missing how
that is something this script would even get involved in. Is your
suggestion to add support for a minimal target that takes a tuned-up
configuration file and returns it to that state, or did you have something
else in mind?
--
* Greg Smith
for me to justify a settings change for
this tool; the whole idea is to pool expert opinion and try to distill it
into code. But that's not good enough for changing that setting for
everybody who installs the database.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
be downloaded from
pgforge. That retreat position goes away if you've commited to putting
the whole thing in core.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Fri, 5 Dec 2008, Robert Haas wrote:
OK, I did this. I actually tried 10 .. 100 in increments of 10 and
then 100 ... 1000 in increments of 50, for 7 different queries of
varying complexity
Great bit of research. Was this against CVS HEAD or an 8.3 database?
--
* Greg Smith [EMAIL
. Knowing that a future 8.5 update could finally blow
away the bogus dropped columns makes leaving them in there for this round
not as bad, and it would avoid needing to mess with the whole
pg_dump/CREATE TABLE with NULL bit.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore
be possible to find a modern system takes a while to
process that much WAL volume. It's pretty rare I run into that (usually
only after I do something abusive), whereas complaints about the logs
filling with checkpoint warnings on systems set to the default seem to pop
up all the time.
--
* Greg Smith
something rather
than tweak the parameters forever. It may be a bit too aggressive as
written right now in those cases.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
strong opinion there either way.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
pgtune.gz
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
. I'm beginning to remember why nobody has ever managed to
deliver a community tool that helps with this configuration task before.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Thu, 4 Dec 2008, Gregory Stark wrote:
Greg Smith [EMAIL PROTECTED] writes:
Is it worse to suffer from additional query overhead if you're sloppy with
the tuning tool, or to discover addition partitions didn't work as you
expected?
Surely that's the same question we faced when deciding
their heads explode at which point all their problems are gone.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
with a larger target which seems weird.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
afraid that may be too late
to implement and still ship the next release on schedule. And if such
bootstrap code is needed, we sure need to make sure the prototype it's
going to be built on is solid ASAP. That's what I want to help you look
into if you can catch me up a bit here.
--
* Greg Smith
person who is frantic that this program isn't being
worked on actively?
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
this
integrated into initdb itself. There were just too many thing to get
under control for that to practical just yet.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
is certainly off-topic for this list though.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Mon, 1 Dec 2008, Tom Lane wrote:
Greg Smith [EMAIL PROTECTED] writes:
I'd ultimately like to use the Python version as a spec to produce a C
implementation, because that's the only path to get something like this
integrated into initdb itself.
It won't get integrated into initdb in any
that slowed
down than the one that improved, understanding that might finally provide
some evidence against increasing it by default.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
on.
-Platform bit width is detected (Python looks at how wide a pointer is to
figure that out), and that's used to figure out whether to load a 32-bit
based set of information from pg_settings or a 64-bit one.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
pgtune-v3
On Sun, 30 Nov 2008, Greg Smith wrote:
Memory detection works on recent (=2.5) version of Python for Windows
now.
I just realized that the provided configuration is really not optimal for
Windows users because of the known limitations that prevent larger
shared_buffers settings from being
thing in the Loose Ends
section of the message.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
, but
if your database doesn't actually create/truncate tables in normal use it
doesn't buy you anything once you're in production.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
going to spook such commercial users, even if it defaults to off.
The privacy issues are one reason I put the web-based port far down
relative to my priorities; another is that I don't do much web application
development. But if somebody else wants to run with that, fine by me.
--
* Greg Smith
reads.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
of polishing at least a week or two before all that work wraps up.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
seems a less
controversial setting.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
if it ends up not being a
setting that is altered.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
, that will be in my next update to this
program.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD#!/usr/bin/python
pg_generate_conf
Sample usage shown by running with --help
import sys
import os
import datetime
import optparse
class PGConfigLine:
Stores the value
to that offline utility could continue after 8.4
proper was completely frozen.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
in
appropriately. Just a thought I wanted to throw out there, if it makes
eventual upgrades from 8.4 more complicated it may not be worth even
considering.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
before accepting. In general here, if it doesn't ship with the
stock Python, there would have to be a really, really compelling reason to
use any external library that adds more dependencies.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing
page that translates the
old name into the new one. But if you were already targeting that page
with a redirect, it would take a double redirect to find the new location,
and that doesn't work. See
http://en.wikipedia.org/wiki/Wikipedia:Double_redirects for more details.
--
* Greg Smith
you're building a config file on a system other than the one it's being
deployed onto.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
is a
couple of steps away from where I'm at right now.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD#!/usr/bin/python
pg_generate_conf
Sample usage:
pg_generate_conf config-file
Reads that config file, updates a few key configuration settings, then
writes result to standard
know only async I/O works on Solaris. Linux
also has an async I/O library, and it's not clear to me yet whether that
might work even better than the fadvise approach.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers
for an example.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
knob you can turn and
benchmark the results at.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
has 32MB of cache in it and you're
seeking around, you've got a pretty big working area relative to how fast
you can fill that with requested data.
And then there's a patch that helps accelerate this process I should get
back to benchmarking again...
--
* Greg Smith [EMAIL PROTECTED] http
This is now the first entry on the new 8.4 Open Items list:
http://wiki.postgresql.org/wiki/PostgreSQL_8.4_Open_Items
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Tue, 7 Oct 2008, Magnus Hagander wrote:
Might this be the time to add an open items for 8.4 page to the wiki?
There's already:
http://wiki.postgresql.org/wiki/Todo:WishlistFor84
Which was aimed at being a live version of that, but was superseded by the
CommitFest pages.
--
* Greg
of
installs to manage and can only reach the hosted server on port 5432
crowds.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
of a
string I have to parse is a long-term win.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
/Eastern | US/Eastern | UNKNOWN
timezone_abbreviations | Default| Default | UNKNOWN
transaction_isolation | read committed | default |
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MDIndex: doc/src/sgml/catalogs.sgml
0.06% of Fibre Channel disks
develop a mismatch during that time.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
to document the two columns
appropriately. One perspective I don't get to see very often is that of a
regular user adjusting their settings.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
because of how the patch was
refactored.
I'm excited to see index scans in the new patch as well, since I've got
1TB of test data that gets navigated that way I can test with.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql
performance
one. Would be nice to get a report from someone running FreeBSD to see
what's needed to make the test script run on that OS.
[1] http://blogs.sun.com/jkshah/entry/postgresql_east_2008_talk_best :
Page 8 of the presentation covers just how limited the default UFS cache
tuning is.
--
* Greg
, presumably you
might as well just read the blocks rather than advise about them when the
seek overhead is close to zero. Should be able to do a RAM disk run as
well.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers
.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
of performance just by disabling the clobber and context
checking, that would be valuable to know. Right now I waste a fair amount
of time running performance and assert builds in parallel.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers
if the actual performance results will be tossed.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
of the software, and there's a big void in that
stack waiting for a database with the right security model to fill. You
are right that getting code contributions back again is a challenge
though.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing
cases for wanting to know it.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MDIndex: doc/src/sgml/catalogs.sgml
===
RCS file: /home/gsmith/cvsrepo/pgsql/doc/src/sgml/catalogs.sgml,v
retrieving revision 2.174
situations and 2) copy the page to somewhere else to tag the one that
goes along with a particular release. If there is some version specific
stuff there it's straightforward to do something along one of those two
lines at the point it's needed.
--
* Greg Smith [EMAIL PROTECTED] http
if the clocks are perfectly synced, by the time the standy
received the transaction it will be later than the original.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
submit right
now won't apply cleanly if the source file/line patch is committed.
If nobody cares about doing that work twice, I'll re-submit a separate
patch once this one is resolved one way or another. I hope you snagged
the documentation update I added to your patch though.
--
* Greg Smith
postgresql.conf files to support a new version. Then the tool can convert
all the places someone uses the old syntax into the new.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
but was getting a little bored
watching everyone replay
http://archives.postgresql.org/pgsql-hackers/2006-07/msg01229.php with
barely any changes from the first time.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers
on
was exactly what the name for it should be, and there I really don't care.
I made the argument for why I named it the way I did, but if it gets
committed with a less friendly name (like boot_val) I won't complain.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
On Thu, 4 Sep 2008, Simon Riggs wrote:
I think this should be organised with different kinds of reviewer...
Great post. Rewrote the intro a bit and turned it into a first bit of
reviewer training material at
http://wiki.postgresql.org/wiki/Reviewing_a_Patch
--
* Greg Smith [EMAIL
feeling that Simon's text was too much; there's value to both a
gentle intro and a detailed list of review tasks.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
getting up to speed to help out with here are
catalog updates and working on integration/testing.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
-+--
262144 | kB
(1 row)
Since the word current isn't actually in the patch anywhere, and only
appears in that little sample usage snippet I provided, whether or not
it's a good name for that doesn't impact the patch itself.
--
* Greg Smith [EMAIL PROTECTED] http
to an easier to use but
slightly ambiguous one, and I'm not going to argue for default further
if everyone else is happy with a cryptic naming instead. The important
thing is that the boot_val gets exposed somehow so tool writers can
trivially present it as an option.
--
* Greg Smith [EMAIL
asks me how can I tell what the default is
for *X*? I want to be able to answer this question with look in
pg_settings, which is easy enough to remember, and not have to say
anything else. That's the source of my mindset here, and I'm sure I'm not
alone in fielding that so often.
--
* Greg
was
actually taken from, and the top 3 obstacles to writing a simple and easy
to use read/modify/write tuning tool are all cleared.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Wed, 3 Sep 2008, Tom Lane wrote:
Greg Smith [EMAIL PROTECTED] writes:
First question--how about if I changed that description to read:
Default value used at server startup if the parameter is not explicitly
set?
... not otherwise set would probably be an accurate phrasing.
(I'm
On Sun, 31 Aug 2008, Alvaro Herrera wrote:
Greg Smith wrote:
This patch does need a bit of general care in a couple of areas. The
reviewing game plan I'm working through goes like this:
Did this review effort go anywhere?
Haven't made much progress--all my spare time for work like
I'd be dumping something
with a filename into tabular output.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
as a guide for what to touch. I'll try to fit that in
this weekend so it makes the commitfest deadline. I'll update the docs
for all the changes (the ones in there already and the one I add) while
I'm at it and submit a combined patch.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com
to the code base, of
course, which it doesn't sound like it is.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
by escaping some characters, that's still very useful to me. I'd
hate to see a focus on the corner cases drive this feature away.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
against breaking it into sections (don't really care either
way), just pointing out that it may not actually be necessary.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
there but that's
clearly not obvious to most people.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
it did to me once) that such a tool would easily follow:
http://pgfoundry.org/docman/?group_id=1000106
The bright side here is that you don't have to waste time tinkering in
this area to find out where the dead ends are like Josh and I
independantly did.
--
* Greg Smith [EMAIL PROTECTED
that was a primary goal
of anything I've said. It just so happens that improving what tuning you
can do over port 5432 helps that crowd out too, that's a bonus as I see
it.
Ask me about EnterpriseDB's On-Demand Production Tuning
...nah, too easy, I'll just let that go.
--
* Greg Smith [EMAIL PROTECTED
tried to quantify the overhead of logging with timestamps on I
couldn't even measure its impact, it was lower than the usual pgbench
noise. That was on Linux. Do you have a suggestion for a platform that
it's a problem on that I might be able to use? I'd like to do some
measurements.
--
* Greg
because the test ran for a
trivial amount of time? Seems like it happens a lot to me. This patch
was already on my todo list for 8.4 and I'm glad I don't have to write it
myself now.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list
hoping to work on the sexy autotuning parts without doing some of the
grunt work, let me know if you can figure out how so I can follow you.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
in postgresql.conf/pg_hba.conf?; see those threads I
mentioned for some context on that.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
+ pg_settings.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
I know some
people wanted to see a more formal document for before mucking with any of
the code. I'll have something to announce there shortly.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
those numbers
actually can be tied to some real-world time measure. If you did that,
you'd actually have a shot at accomplishing the real goal here, making
statement_cost_limit cut off statements expected to take longer than
statement_timeout before they even get started.
--
* Greg Smith [EMAIL
in the middle there to make that straightforward.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
1201 - 1300 of 1566 matches
Mail list logo
