Re: [PATCHES] [DOCS] OS/X startup scripts
On Wed, May 16, 2007 at 09:12:23AM +0100, Heikki Linnakangas wrote: > Jim C. Nasby wrote: > >BTW, is there some trick to getting cvs diff to ignore files that > >aren't in the repo? > > Trick? That's what it does by default. I suspect he's talking about all the lines starting with '?' that diff produces. Lacking sophistication, I've been known to do: cvs diff [list of files here] |grep -v '^?' > the_file.diff Cheers, D -- David Fetter <[EMAIL PROTECTED]> http://fetter.org/ phone: +1 415 235 3778AIM: dfetter666 Skype: davidfetter Remember to vote! Consider donating to PostgreSQL: http://www.postgresql.org/about/donate ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [PATCHES] [DOCS] OS/X startup scripts
On Wed, May 16, 2007 at 09:12:23AM +0100, Heikki Linnakangas wrote: > Jim C. Nasby wrote: > >BTW, is there some trick to getting cvs diff to ignore files that aren't > >in the repo? > > Trick? That's what it does by default. Well, it throws a notice that they're there... [EMAIL PROTECTED]:34]~/pgsql/HEAD/src:22%cvs diff ? Makefile.global ? backend/postgres ? backend/access/common/.deps ? backend/access/gin/.deps ... Granted, I could run that through grep, but I'm not sure that's 100% safe. -- Jim Nasby [EMAIL PROTECTED] EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [PATCHES] [DOCS] OS/X startup scripts
Jim C. Nasby wrote: > On Wed, May 16, 2007 at 09:12:23AM +0100, Heikki Linnakangas wrote: > > Jim C. Nasby wrote: > > >BTW, is there some trick to getting cvs diff to ignore files that aren't > > >in the repo? > > > > Trick? That's what it does by default. > > Well, it throws a notice that they're there... > > [EMAIL PROTECTED]:34]~/pgsql/HEAD/src:22%cvs diff > ? Makefile.global What I do is build somewhere else. Thus the only files present in the source dir and not in the repo are those generated by bison/flex, which are in .cvsignore and are thus not displayed. That said, check this out: http://www.ubiobio.cl/~gpoo/pgsql/settings/ Sadly, usage instructions are in spanish only currently, but I claim that this script is extremely useful for Pg development (sure, I wrote it and tailored to my needs). If there is interest I can translate the docs, but I have posted the script in these lists before and got no much of an interest. Michael Glaesemann did find it useful when I showed it to him in the summit, though. -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [PATCHES] [DOCS] OS/X startup scripts
On Wed, May 16, 2007 at 03:53:22PM +0100, Gregory Stark wrote: > "David Fetter" <[EMAIL PROTECTED]> writes: > > > On Wed, May 16, 2007 at 09:12:23AM +0100, Heikki Linnakangas wrote: > >> Jim C. Nasby wrote: > >> >BTW, is there some trick to getting cvs diff to ignore files > >> >that aren't in the repo? > >> > >> Trick? That's what it does by default. > > > > I suspect he's talking about all the lines starting with '?' that > > diff produces. > > > > Lacking sophistication, I've been known to do: > > > > cvs diff [list of files here] |grep -v '^?' > the_file.diff > > Those lines go to stderr. Not when I do "cvs diff." Is there something I should (un)set in my .cvsrc? > If you do "cvs diff > file" it spits out all the cvs file statuses > to the terminal but dumps the diff to the file. > > It doesn't matter, diffs can contain arbitrary junk between the file > diffs. patch only looks at the things it recognizes. IMHO, the diffs also need to be human-readable, and 500 useless lines starting with "?" don't help with that. Cheers, D -- David Fetter <[EMAIL PROTECTED]> http://fetter.org/ phone: +1 415 235 3778AIM: dfetter666 Skype: davidfetter Remember to vote! Consider donating to PostgreSQL: http://www.postgresql.org/about/donate ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] [DOCS] row-level stats and last analyze time
Has this been done yet? I don't think so. --- Tom Lane wrote: > Neil Conway <[EMAIL PROTECTED]> writes: > > On Thu, 2007-26-04 at 18:07 -0400, Neil Conway wrote: > >> (1) I believe the reasoning for Tom's earlier change was not to reduce > >> the I/O between the backend and the pgstat process [...] > > > Tom, any comments on this? Your change introduced an undocumented > > regression into 8.2. I think you're on the hook for a documentation > > update at the very least, if not a revert. > > The documentation update seems the most prudent thing to me. The > problem with the prior behavior is that it guarantees that every table > in the database will eventually have a pg_stat entry, even if > stats_row_level and stats_block_level are both off. In a DB with lots > of tables that creates a significant overhead *for a feature the DBA > probably thinks is turned off*. This is not how it worked before 8.2, > and so 8.2.0's behavior is arguably a performance regression compared > to 8.1 and before. > > Now this patch went in before we realized that 8.2.x had a bug in > computing the stats-file-update delay, and it could be that after fixing > that the problem is not so pressing. But I don't particularly care for > new features that impose a performance penalty on those who aren't using > them, and that's exactly what last_vacuum/last_analyze tracking does if > we allow it to bloat the stats file in the default configuration. > > The long-term answer of course is to devise a more efficient stats > reporting scheme, but I'm not sure offhand what that would look like. > > regards, tom lane > > ---(end of broadcast)--- > TIP 7: You can help support the PostgreSQL project by donating at > > http://www.postgresql.org/about/donate -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [PATCHES] [DOCS] OS/X startup scripts
David Fetter wrote: cvs diff [list of files here] |grep -v '^?' > the_file.diff Those lines go to stderr. Not when I do "cvs diff." Is there something I should (un)set in my .cvsrc? No. (The lines that go to stderr are the directory names). But I don't see why there's a problem with using the command above. Or if you prefer, use something like this to postprocess the file: perl -ni -e 'print unless /^\?/;' diff-file Bottom line - TIMTOWTDI cheers andrew ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [PATCHES] [DOCS] OS/X startup scripts
On May 16, 2007, at 9:38 , Alvaro Herrera wrote: That said, check this out: http://www.ubiobio.cl/~gpoo/pgsql/settings/ Sadly, usage instructions are in spanish only currently, but I claim that this script is extremely useful for Pg development (sure, I wrote it and tailored to my needs). If there is interest I can translate the docs, but I have posted the script in these lists before and got no much of an interest. Michael Glaesemann did find it useful when I showed it to him in the summit, though. Ooo! Nifty! I'll have to check out what's changed. I still use this script. I find it very helpful. I can post my tweaks as well, if there's interest. Michael Glaesemann grzm seespotcode net ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [PATCHES] [DOCS] OS/X startup scripts
Michael Glaesemann wrote: > > On May 16, 2007, at 9:38 , Alvaro Herrera wrote: > > >That said, check this out: > > > >http://www.ubiobio.cl/~gpoo/pgsql/settings/ > > > >Sadly, usage instructions are in spanish only currently, but I claim > >that this script is extremely useful for Pg development (sure, I wrote > >it and tailored to my needs). If there is interest I can translate > >the > >docs, but I have posted the script in these lists before and got no > >much > >of an interest. Michael Glaesemann did find it useful when I > >showed it > >to him in the summit, though. > > Ooo! Nifty! I'll have to check out what's changed. I still use this > script. I find it very helpful. I can post my tweaks as well, if > there's interest. Yes, there is. The one thing I did not keep was the stuff about the env vars, because it didn't suit me to be copying and pasting them with the mouse. To solve the autocompletion problem you had that prompted you to tweak it, what I do is runpg 00 ` Ctrl-A ` so the autocompletion works because the first work is "runpg" and not the single quote, and I enter the initial quote when the command has been completed (Ctrl-A moves to the start of the line). I can't remember if I dropped something else. -- Alvaro Herrerahttp://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
