Re: [HACKERS] Need a mentor, and a project.

people show up with patches where the solution was just add threading to the back-end here... which might seem completely reasonable to someone new--but it will never get committed. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www

Re: [HACKERS] Has anyone used CLANG yet?

code out PostgreSQL, that's the other approach. -- 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

Re: [HACKERS] tsearch parser inefficiency if text includes urls or emails - new version

that boring stuff. I tried to make it automate the most tedious parts of both development and patch review. Documentation and the program itself are at the git repo Kevin mentioned. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www

Re: [HACKERS] More broken links in documentation

at http://www.sco.com/skunkware/ -- 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] tsearch parser inefficiency if text includes urls or emails - new version

when it decides you need to build, so it can try to do the right thing in either case. My hope was that anyone who tried peg out would find it a net positive time savings after a single use, glad to hear I accomplished that in your case. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL

Re: [HACKERS] More broken links in documentation

Magnus Hagander wrote: ftp://ftp.ora.com/pub/examples/nutshell/ujip/doc/cjk.inf in charset.sgml, detailed info about some charsets. Do we just remove this? Anybody know if similar info is available elsewhere? Now http://examples.oreilly.com/cjkvinfo/doc/cjk.inf -- Greg Smith2ndQuadrant

Re: [HACKERS] tsearch parser inefficiency if text includes urls or emails - new version

more information about it tonight too. -- 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

Re: [HACKERS] [PATCH] dtrace probes for memory manager

of memory will be thrown around: pgbench -i -s 10 db pgbench -S -c 10 -T 600 db That will do just SELECT statements against a much smaller database (about 160MB) and will run for 10 minutes each time. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g

Re: [HACKERS] Adding support for SE-Linux security

/design, which is really uncomfortable given how things work here. -- 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] YAML Was: CommitFest status/management

talking about: http://archives.postgresql.org/message-id/20091130123456.4a03.52131...@oss.ntt.co.jp is the candidate for commit that includes the cleanup you've already done. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www

Re: [HACKERS] [PATCH] Windows x64 [repost]

development is going to wait for if it doesn't get finished up before the CommitFest is over. You're basically at Magnus's mercy though, if he wants to dedicate enough time to get it done that certainly can happen. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g

Re: [HACKERS] ProcessUtility_hook

the hook for this one; it looks ready for committer to me. -- 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

Re: [HACKERS] EXPLAIN BUFFERS

suggestion's for rewording. I linked to both of those messages in the CF app, labeled as notes the committer might want to consider, but that the patch hasn't been updated to include yet. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www

Re: [HACKERS] [patch] pg_ctl init extension

. There's only one bit that sticks out oddly now: + Note: The commandinitdb/command might be invoked by + commandpg_ctl initdb/command and commandinitdb/command cannot be in + default path on a productnamePostgreSQL/productname installations. What is that supposed to mean exactly? -- Greg

Re: [HACKERS] ProcessUtility_hook

-off practice works on some other projects. -- 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

Re: [HACKERS] YAML Was: CommitFest status/management

done here. -- 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

Re: [HACKERS] new CommitFest states (was: YAML)

Robert Haas wrote: On a related note, Greg Smith requested a state called Discussing Review, which would logically follow Needs Review and precede Waiting for Author/Ready for Committer/Returned with Feedback. I'm not altogether convinced of the value of that state, but I'm not altogether

Re: [HACKERS] strange segfault with 8.3.8

we had some corrupted pages (//ERROR/: /compressed data/ is corrupt/). Random segfaults only under heavy load with corrupted pages afterwards normally means bad RAM. I'd suggest a round of memtest86+ on the system if it's PC hardware. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL

Re: [HACKERS] YAML

patch than to make it wait for this. -- 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

Re: [HACKERS] Install chapter broken link

link above, and at http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/gettext/ Even Solaris aims to be compatible with the GNU version as of 2004. I think http://www.gnu.org/software/gettext/ is the appropriate new link destination. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL

Re: [HACKERS] Adding support for SE-Linux security

input here beyond that offered by the patch author, who's obviously qualified but at the end of the day is still only one opinion. He's also not in a good position to tell other people their ideas are misinformed either. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services

Re: [HACKERS] EXPLAIN BUFFERS

you have are text logs around (split on : then =). It might be too compressed down for some tastes though. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com

Re: [HACKERS] EXPLAIN BUFFERS

=1 width=4) Which seems to be what was being emulated here. I though that was pretty reasonable given this is a related feature. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via pgsql-hackers mailing

Re: [HACKERS] A sniffer for the buffer

implementation that's used pretty often by developers here named dbt-2: http://wiki.postgresql.org/wiki/DBT-2 that will work with a newer version. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via pgsql

Re: [HACKERS] A sniffer for the buffer

a mistake--if you want to hack on the PostgreSQL code, you should be using at least PostgreSQL 8.4, and it's better still to checkout from the CVS/git repos. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com

Re: [HACKERS] Clearing global statistics

Itagaki Takahiro wrote: Greg Smith g...@2ndquadrant.com wrote: -Not sure if this should be named pg_stat_rest_global (to match the way these are called global stats in the source) or pg_stat_reset_cluster. Picked the former for V1, not attached to that decision at all. Might even make

[HACKERS] Wrapping up CommitFest 2009-11

). This will leave some time for their authors to respond to feedback before we close up here, and of course we still have one more CommitFest left for patches that are returned with feedback to be resubmitted for. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support

Re: [HACKERS] Clearing global statistics

Itagaki Takahiro wrote: Greg Smith g...@2ndquadrant.com wrote: I'm thinking that I should rename this new function to pg_stat_reset_bgwriter so it's obvious how limited its target is. I don't think it is a good name because we might have another cluster-level statictics not related

Re: [HACKERS] tsearch parser inefficiency if text includes urls or emails - new version

of implementation rather than specific functional bits, I'm leaning toward saying this one is ready to have a committer look at it. Any comments from Kevin or Andres about where this is at? -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www

Re: [HACKERS] Syntax for partitioning

, so that the rest of the partitioning patch ideas floating around finally have a firm place to start attaching to. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql

Re: [HACKERS] add more frame types in window functions (ROWS)

committed in our next CF. -- 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

Re: [HACKERS] [patch] pg_ctl init extension

left you need to do. -- 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

Re: [HACKERS] YAML Was: CommitFest status/management

an improvement. Consider me a neutral vote, although I suspect the above may sway some people who were on the fence toward disapproval. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list

Re: [HACKERS] [PATCH] Largeobject Access Controls (r2460)

a committer willing to chew on it. I think those are the main hurdles left for this patch. -- 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

Re: [HACKERS] LDAP where DN does not include UID attribute

obvious none of our other reviewers are going to be able to do anything with it. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com

Re: [HACKERS] Listen / Notify - what to do when the queue is full

worked out and it could turn into a useful feature--I know I've wanted NOTIFY with a payload for a years. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com

Re: [HACKERS] pgbench: new feature allowing to launch shell commands

it's less likely to be rejected for the code is ugly reasons if that's done first. That sort of rejection is always a real possibility with this project, particularly for something like this where it's not as obvious to everyone what the feature is useful for. -- Greg Smith2ndQuadrant

[HACKERS] Clearing global statistics

. Since this whole patch is basically a cut and paste job of code that was already there, I don't really expect it to need much discussion beyond these minor points; wouldn't have sent it in the middle of an active CommitFest if that weren't the case. -- Greg Smith2ndQuadrant Baltimore, MD

Re: [HACKERS] [PATCH] Largeobject Access Controls (r2432)

it only mentions version numbers that are historical rather than future. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com

Re: [HACKERS] [PATCH] Largeobject Access Controls (r2432)

, the two examples you gave are certainly good for showing the standard practices used here. Specific version numbers are strewn all about, and if there's commits mentioning 8.5 already in there one more won't hurt. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services

Re: [HACKERS] Page-level version upgrade (was: Block-level CRC checks)

that we didn't even get to the last time, because showstopper issues popped up first. That problem was looming had work continued down that path though. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via

Re: [HACKERS] Page-level version upgrade (was: Block-level CRC checks)

and free some space on them The pre-upgrade utility we've been talking about does (2), and that's easy to imagine implementing as an add-on module rather than a backport. I don't know how (1) can be done in a way such that it's easily backported to 8.4. -- Greg Smith2ndQuadrant Baltimore

Re: [HACKERS] Page-level version upgrade (was: Block-level CRC checks)

Robert Haas wrote: On Wed, Dec 2, 2009 at 1:56 PM, Greg Smith g...@2ndquadrant.com wrote: There's no reason the associated catalog support had to ship with the old version. You can always modify the catalog after initdb, but before running the pre-upgrade utility. pg_migrator might make

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

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

distant future for a platform that integrates 8.4 from day one; I didn't think that deploying RHEL5 was going to be the only choice for too much longer. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via pgsql

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

Tom Lane wrote: Greg Smith g...@2ndquadrant.com writes: What I was trying to suggest was that right now, there are situations where a new deployment on 8.1 is still completely reasonable and possible to justify in the Enterprise Linux space, whereas I don't know of any situation where 7.4

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

the last year in the field. -- 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] Page-level version upgrade (was: Block-level CRC checks)

for them is that you can dial up its intensity to exactly how much overhead you can stand, and let it loose until it's done. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list

Re: [HACKERS] pgbench: new feature allowing to launch shell commands

, it was on the edge of that before you started--and these two new commands are by far the most complicated. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com skewed-acct.pl Description: Perl program \set naccounts

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: [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] 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] 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] 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] 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] 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] 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] 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] next CommitFest

part here remains finding reviewers for the really big patches. -- 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] write ahead logging in standby (streaming replication)

synchronous behavior; you have to pick one. The best you can do if you need both is work on accelerating fsync everywhere using the standard battery-backed write cache technique. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www

[HACKERS] CommitFest 2009-11 Call for Reviewers

. Those are not so easy to just split among multiple people due to how they relate to one another. -- 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: [HACKERS] [RRR] CommitFest 2009-11 Call for Reviewers

Josh Berkus wrote: On 11/12/09 9:45 AM, Greg Smith wrote: For lack of a more qualified volunteer, I'll be handling the initial round of patch assignments and reviewer organization. Hmmm? Who's more qualified than you, exactly? I was alluding to the fact that Robert isn't

Re: [HACKERS] CommitFest 2009-11 Call for Reviewers

of them to handle two, that should be all it takes for this round. Will move the rest of the discussion here to just rrreviewers. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via pgsql-hackers mailing

Re: [HACKERS] Patch committers

a case that someone who's gotten skilled enough as a reviewer to only pass through patches of that quality should get some recognition even if they didn't write them. That's clearly a useful subset of the skills needed to commit patches only if they look to be ready for it. -- Greg Smith

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

replication nowadays. That's an awful name though, because it's not true--that's asynchronous replication, just aiming for minimal lag. It's OK to say that's what you want, but you can't say it's really a synchronous commit anymore if you do things that way. -- Greg Smith2ndQuadrant

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

synchronous thinking it's a shared term also applicable to the semi-synchronous variations here, that's just going to be confusing for everyone. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via pgsql-hackers

Re: [HACKERS] [PATCH] SE-PgSQL/lite (r2429)

a major design issue in the early 8.4 versions of SEPostgreSQL, and that as you say you've been working on that. I'm not sure what relationship there is between those two today though, or exactly where the general non-SELinux row filtering is at on the roadmap. -- Greg Smith2ndQuadrant Baltimore

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

Fujii Masao wrote: On Fri, Nov 13, 2009 at 1:49 PM, Greg Smith g...@2ndquadrant.com wrote: Right, those are the possibilities, all four of them have valid use cases in the field and are worth implementing. I don't like the label semi-synchronous replication myself, but it's a valuable

Re: [HACKERS] [PATCH] SE-PgSQL/lite (r2429)

for clarifying where things are at. -- 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

Re: [HACKERS] Patch committers

capabilities. I seriously doubt you're going to find a new committer jumping right in by committing hot standby out of the gate just because they could do so. -- Greg Smith2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support g...@2ndquadrant.com www.2ndQuadrant.com -- Sent via

Re: [HACKERS] Patch committers

without actually getting your hands into the details. -- 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] Patch committers

switching Zoom to show 10 years. -- 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] next CommitFest

Selena Deckelmann wrote: On Tue, Nov 10, 2009 at 10:40 PM, Greg Smith gsm...@gregsmith.com wrote: I was just poking around on the Wiki, and it looks like the role of the CommitFest manager isn't very well documented yet. It's pretty straightforward. Robert has actually done a great

Re: [HACKERS] next CommitFest

that, but this one looks smaller and with more familiar patches than those. -- 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] next CommitFest

of the schedule for 8.5 on the Wiki itself. Could you find some time this week to rattle off an outline of the work involved? It's hard to decide whether to volunteer to help without having a better idea of what's required. -- * Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD

Re: [HACKERS] Patch set under development to add usage reporting.

against a more stable version like 8.4.1, if you must target something people can also deploy, but even that's not ideal and will eventually turn into a code merge hurdle. -- * Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD -- Sent via pgsql-hackers mailing list (pgsql

Re: [HACKERS] Parsing config files in a directory

postgresql.conf lines that crashed my Python code as people submit bug reports with those. You might be surprised at all of the places people put whitespace at. -- * Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] Parsing config files in a directory

a working prototype out the door, rather than properly the whole grammar. -- * 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

Re: [HACKERS] Parsing config files in a directory

appeared upstream. Stuff in PGDATA is all yours and not tracked as a config file. -- * 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

Re: [HACKERS] Parsing config files in a directory

of this discussion, this is the point where someone pops up and says that switching to XML for the postgresql.conf will solve this problem. Whoever does that this time goes into the ring with Kevin and I, but they don't get a club. (All fight proceeds to benefit SPI of course). -- * Greg Smith gsm

Re: [HACKERS] Parsing config files in a directory

this is not trivial to do well. -- * 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

Re: [HACKERS] Parsing config files in a directory

patch anyway, we can bikeshed more after it's been submitted. One file per GUC is certainly never going to fly though, it's been hard enough getting people to accept going from one file to more than one. -- * Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD -- Sent via

Re: [HACKERS] Parsing config files in a directory

conference! -- * 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

Re: [HACKERS] Parsing config files in a directory

plan to work. -- * 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

Re: [HACKERS] Parsing config files in a directory

for the painful parts. I wish I could share all of the postgresql.conf files I've seen so you could better appreciate how people torture the poor file in the field. -- * Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] Parsing config files in a directory

is make a path where new users who don't ask for anything special get a setup that's easy for tools to work on, while not completely deprecating the old approach for those who want it--but you have to ask for it. -- * Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD -- Sent via

Re: [HACKERS] Parsing config files in a directory

a solution to this problem that handles any sort of way users can mess with the configuration. One might even make a case that this tool should get run just after every time the server starts successfully. -- * Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD -- Sent via

Re: [HACKERS] Parsing config files in a directory

in alphabetical order. -- * 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

Re: [HACKERS] Parsing config files in a directory

that. This is easy to handle by hand, but hard to get a program to do in a way that satisfies what everyone is looking for. Raising the bar for tool-assisted changes (and I'm including SET PERSISTENT in that category) like that is one reason so few such tools have been written. -- * Greg Smith gsm

Re: [HACKERS] Parsing config files in a directory

in the default configuration less objectionable. -- * 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

Re: [HACKERS] Parsing config files in a directory

it just encourages argument. The goal here is to add flexibility and ways people can choose to work with the configuration, not to replace what's being done now outright with an approach everyone must adopt. -- * Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD -- Sent via

<    6   7   8   9   10   11   12   13   14   15   >