Re: [HACKERS] posix advises ...

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

Re: [EMAIL PROTECTED]: Re: [HACKERS] [patch] GUC source file and line number]

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

Re: [HACKERS] [patch] GUC source file and line number]

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

Re: [HACKERS] [patch] GUC source file and line number]

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

Re: [HACKERS] [patch] GUC source file and line number]

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

Re: [HACKERS] [patch] GUC source file and line number]

-+-- 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

Re: [HACKERS] Need more reviewers!

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

Re: [HACKERS] Need more reviewers!

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

Re: [HACKERS] Prototype: In-place upgrade v02

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

Re: [EMAIL PROTECTED]: Re: [HACKERS] [patch] GUC source file and line number]

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

Re: [HACKERS] Move src/tools/backend/ to wiki

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

Re: [HACKERS] Some newbie questions

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

Re: [EMAIL PROTECTED]: Re: [HACKERS] [patch] GUC source file and line number]

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

Re: [HACKERS] [PATCH] Cleanup of GUC units code

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

Re: [HACKERS] [PATCH] Cleanup of GUC units code

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

[HACKERS] Add default_val to pg_settings

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

Re: [HACKERS] Proposal of SE-PostgreSQL patches (for CommitFest:Sep)

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

Re: [HACKERS] Assert Levels

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

Re: [HACKERS] Assert Levels

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

[HACKERS] Initial prefetch performance testing

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

Re: [HACKERS] Initial prefetch performance testing

, 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

Re: [HACKERS] Initial prefetch performance 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://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Initial prefetch performance testing

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

Re: [HACKERS] Add default_val to pg_settings

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

Re: [HACKERS] Block-level CRC checks

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

Re: [HACKERS] Add default_val to pg_settings

/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

Re: [HACKERS] Shouldn't pg_settings.enumvals be array of text?

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

Re: [HACKERS] Shouldn't pg_settings.enumvals be array of text?

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

Re: [HACKERS] Shouldn't pg_settings.enumvals be array of text?

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

Re: [HACKERS] Shouldn't pg_settings.enumvals be array of text?

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

Re: [HACKERS] How is random_page_cost=4 ok?

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

Re: [HACKERS] How is random_page_cost=4 ok?

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

Re: [HACKERS] Debian no longer dumps cores?

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

Re: [HACKERS] Multi CPU Queries - Feedback and/or suggestions wanted!

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

[HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Where to point CommitFestOpen?

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] [WIP] In-place upgrade

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

Re: [HACKERS] [WIP] In-place upgrade

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

Re: [HACKERS] Simple postgresql.conf wizard

, 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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Updated posix fadvise patch v19

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

Re: [HACKERS] Enabling archive_mode without restart

, 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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Simple postgresql.conf wizard

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

[HACKERS] In-place upgrade: catalog side

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Simple postgresql.conf wizard

. -- * 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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Simple postgresql.conf wizard

. 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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] In-place upgrade: catalog side

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

Re: [HACKERS] In-place upgrade: catalog side

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] In-place upgrade: catalog side

. -- * 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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] In-place upgrade: catalog side

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

Re: [HACKERS] default statistics target testing (was: Simple postgresql.conf wizard)

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

Re: [HACKERS] In-place upgrade: catalog side

. 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

Re: [HACKERS] [patch] pg_upgrade script for 8.3-8.4

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

Re: [HACKERS] contrib/pg_stat_statements 1202

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

Re: [HACKERS] Mostly Harmless: Welcoming our C++ friends

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

Re: [HACKERS] Mostly Harmless: Welcoming our C++ friends

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

Re: [HACKERS] Mostly Harmless: Welcoming our C++ friends

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

Re: [HACKERS] default statistics target testing (was: Simple postgresql.conf wizard)

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

Re: [HACKERS] Simple postgresql.conf wizard

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

Re: [HACKERS] Mostly Harmless: Welcoming our C++ friends

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

Re: [HACKERS] contrib/pg_stat_statements 1202

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

Re: [HACKERS] commitfest patch move unavailable

common topics and fill then all in when the CF is created? -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

[HACKERS] CommitFest 2009-11 Closed; Initial assignments

had the ability to test DTrace code in the first round. I'd welcome a review volunteer who is looking to play with DTrace to take a look at either or both patches. If that doesn't happen, eventually I'll just review them myself. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL

Re: [HACKERS] write ahead logging in standby (streaming replication)

synchronous implementation are documented. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org

Re: [HACKERS] Partitioning option for COPY

* if you're doing performance testing. The asserts slow things down enough (particularly with large shared_buffers values) to skew performance tests, but in all other coding situations you should have them enabled. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services

Re: [HACKERS] plpgsql: open for execute - add USING clause

to pay attention to and what should be ignored for now. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription

Re: [HACKERS] CommitFest expectations

out how things fit together than it should be. I started cleaning that up with refreshing http://wiki.postgresql.org/wiki/CommitFest , which is probably the right place to document general rules and expectations better. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services

Re: [HACKERS] enable-thread-safety defaults?

Peter Eisentraut wrote: I don't have a good overview over how many platforms would be affected The anniversary of this thread is a few days early: http://archives.postgresql.org/message-id/492ea404.5080...@esilo.com -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training

Re: [HACKERS] Hot standby and removing VACUUM FULL

. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Partitioning option for COPY

just talking about things. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org

Re: [HACKERS] Partitioning option for COPY

for 8.5--but only if everyone is clear on exactly what direction to push toward. I'm going to reread the history here myself and see if I can write something helpful here. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com

Re: [HACKERS] [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION

is accepted as a reasonable one, as Dan suggested a next step might even be to similarly allow passing COPY FROM through a UDF, which has the potential to provide a new efficient implementation path for some of the custom input filter requests that pop up here periodically. -- Greg Smith

Re: [HACKERS] [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION

in terms of the new function interface, which has the potential to make the COPY implementation cleaner rather than more cluttered (as long as the performance doesn't suffer). -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www

Re: [HACKERS] Syntax for partitioning

feature set here is really remarkable when you see them all together. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

Re: [HACKERS] [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION

the result through the same basic code path as WITH RECORDS, so having both available shouldn't increase the size of the implementation that much. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via pgsql

Re: [HACKERS] cvs chapters in our docs

available since shortly after their respective creation dates, I'm not sure what one could criticize about them as an information source in this area. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via

Re: [HACKERS] New VACUUM FULL

Itagaki Takahiro wrote: Done. (vacuum-full_20091130.patch) Is this ready for a committer now? Not sure whether Jeff intends to re-review here or not, given that the suggestions and their fixes were pretty straightforward. It looks pretty solid at this point to me. -- Greg Smith

Re: [HACKERS] [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION

Jeff Davis wrote: COPY target FROM FUNCTION foo() WITH RECORDS; In what format would the records be? What was your intended internal format for this form to process? -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www

Re: [HACKERS] CommitFest status/management

if we want to shorten the whole process a bit. I don't think that's really what you want though. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org

Re: [CORE] [HACKERS] EOL for 7.4?

and the bugs they might run into aren't that serious. This is not the case at all for either 7.4 or 8.0, which have been completely indefensible as versions to consider deploying for quite some time already. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g

  1   2   3   4   5   6   7   8   9   10   >