Re: [PATCHES] [DOCS] OS/X startup scripts

2007-05-16 Thread Jim C. Nasby
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&#x

Re: [PATCHES] [DOCS] OS/X startup scripts

2007-05-15 Thread Jim C. Nasby
On Tue, May 15, 2007 at 03:35:45PM +1200, Mark Kirkwood wrote: > Alvaro Herrera wrote: > >Mark Kirkwood wrote: > >>Alvaro Herrera wrote: > > > >>>Except that it also includes diffs for generated files, which tend to be > >>>huge. To work around that you need to create a list of files to > >>>exclu

Re: [DOCS] Documentation of pg_badkend_pid and stats functions

2007-05-13 Thread Jim C. Nasby
monfunc2.patch Description: Binary data On Sun, May 13, 2007 at 06:48:01PM -0400, Tom Lane wrote: Jim Nasby <[EMAIL PROTECTED]> writes: System Information Functions +In addition to the functions listed in this section, there are a number of +functions related to the stati

Re: [DOCS] [GENERAL] PITR and tar

2007-05-13 Thread Jim C. Nasby
Moving to -docs... Does anyone know what the history of the docs saying that GNU tar had issues with files changing underneath it? According to this report it's actually BSD tar that has the issue. On Wed, May 09, 2007 at 10:19:05AM -0700, Jeff Davis wrote: > On Wed, 2007-05-09 at 11:40 -0500, Ji

Re: [DOCS] [HACKERS] Replication documentation addition

2006-10-26 Thread Jim C. Nasby
On Thu, Oct 26, 2006 at 11:59:57AM -0400, Bruce Momjian wrote: > Jim C. Nasby wrote: > > On Wed, Oct 25, 2006 at 08:42:07PM -0400, Bruce Momjian wrote: > > > Jim C. Nasby wrote: > > > > Something else worth doing though is to have a paragraph explaining why > >

Re: [DOCS] [HACKERS] Replication documentation addition

2006-10-26 Thread Jim C. Nasby
On Wed, Oct 25, 2006 at 08:42:07PM -0400, Bruce Momjian wrote: > Jim C. Nasby wrote: > > Something else worth doing though is to have a paragraph explaining why > > there's no built-in replication. I don't have time to write something > > right now, but I can do it l

Re: [DOCS] [HACKERS] Replication documentation addition

2006-10-25 Thread Jim C. Nasby
On Wed, Oct 25, 2006 at 04:42:17PM -0400, Bruce Momjian wrote: > Dawid Kuroczko wrote: > > Bruce, I've read Your documentation and I was left a bit with a feeling > > that it's a bit too generic. It's almost as if it could be about just about > > any major database, not PostgreSQL specific. I fee

Re: [DOCS] [HACKERS] Replication documentation addition

2006-10-25 Thread Jim C. Nasby
On Wed, Oct 25, 2006 at 11:38:11AM +0200, Markus Schiltknecht wrote: > I can't really get excited about the exclusion of the term > 'replication', because it's what most people are looking for. It's a > well known term. Sorry if it sounded that way, but I've not meant to > avoid that term. > I

Re: [DOCS] [HACKERS] Replication documentation addition

2006-10-25 Thread Jim C. Nasby
On Wed, Oct 25, 2006 at 08:22:25PM +0930, Shane Ambler wrote: > Bruce Momjian wrote: > > >OK, does that mean we mention EnterpriseDB in the section about Oracle > >functions? Why not mention MS SQL if they have a better solution? I > >just don't see where that line can clearly be drawn on what t

Re: [DOCS] [HACKERS] Replication documentation addition

2006-10-24 Thread Jim C. Nasby
On Tue, Oct 24, 2006 at 03:33:03PM -0700, Joshua D. Drake wrote: > Simon Riggs wrote: > > On Tue, 2006-10-24 at 15:13 -0700, Joshua D. Drake wrote: > > > >> If it were me, I would say that the replication option has to be > >> specific to PostgreSQL (e.g; cjdbc or synchronous jakarta pooling > >>

Re: [DOCS] [HACKERS] Replication documentation addition

2006-10-24 Thread Jim C. Nasby
On Mon, Oct 23, 2006 at 11:39:34PM -0400, Bruce Momjian wrote: > Query Broadcast Replication > --- > > This involves sending write queries to multiple servers. Read-only > queries can be sent to a single server because there is no need for all > servers to process it. Th

Re: [DOCS] [HACKERS] timestamptz alias

2006-10-03 Thread Jim C. Nasby
Moving to -docs On Tue, Oct 03, 2006 at 12:13:46PM -0400, Andrew Dunstan wrote: > Tom Lane wrote: > >Markus Schaber <[EMAIL PROTECTED]> writes: > > > >>Here's a small patch that adds an appropriate explanation. > >> > > > >If we're going to document these aliases, what of float4, float8, and

Re: [DOCS] [HACKERS] Broken link in PG docs

2006-09-25 Thread Jim C. Nasby
Moving to -docs On Mon, Sep 25, 2006 at 04:44:47PM +0530, Gurjeet Singh wrote: > At the end of the following page: > > http://www.postgresql.org/docs/8.0/static/indexes-partial.html > > there is a link [Generalized Partial > Indexes

Re: [DOCS] [GENERAL] TOAST not working

2006-06-10 Thread Jim C. Nasby
Dropping -general On Sat, Jun 10, 2006 at 10:58:49PM -0400, Tom Lane wrote: > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > Actually, it's BLCKSZ/4. From > > http://www.postgresql.org/docs/8.1/interactive/storage-toast.html: > > > "The TOAST co

Re: [DOCS] [GENERAL] TOAST not working

2006-06-10 Thread Jim C. Nasby
org/docs/8.1/interactive/storage-toast.html: "The TOAST code is triggered only when a row value to be stored in a table is wider than BLCKSZ/4 bytes (normally 2Kb)." BTW, 'row value' seems a bit prone to confusion (could be interpreted as the row itself). It'd probably be

Re: [DOCS] Mention pg_dump version portability

2006-05-17 Thread Jim C. Nasby
ame as the text/SQL dump, just with some fancy wrappers around it? -- Jim C. Nasby, Database Architect[EMAIL PROTECTED] Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tom

Re: [DOCS] Mention pg_dump version portability

2006-05-16 Thread Jim C. Nasby
On Mon, May 15, 2006 at 07:43:20PM -0400, Bruce Momjian wrote: > Jim C. Nasby wrote: > > On Sat, May 13, 2006 at 12:21:06PM -0400, Bruce Momjian wrote: > > > I have applied this patch that mentions pg_dump portability to 8.1.X and > > > CVS HEAD. > > > > W

Re: [DOCS] Mention pg_dump version portability

2006-05-15 Thread Jim C. Nasby
don't think I've ever seen problem with the custom format (though this could just be because everyone uses the default...) -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.n

Re: [DOCS] [GENERAL] COPY command documentation

2006-03-24 Thread Jim C. Nasby
that doc patches be > > sent to -docs. > > > > What say? > > I say no, because whilst some comments should (and do) end up in the docs, > many are simply useful real-world code examples and related information that > people post. It's useful stuff, but would clutter

Re: [DOCS] Online Backups: Minor Caveat, Major Addition?

2006-03-22 Thread Jim C. Nasby
mand including a way to interrupt in the event of a need > for actual failover-style recovery before I could draft 23.3.3.3, > though. BTW, when it comes to continuous recovery you should have a look at http://pgfoundry.org/projects/pgpitrha/ -- Jim C. Nasby, Sr. Engineering Consultant

Re: [DOCS] Get docs for contrib on the web somewhere

2006-03-17 Thread Jim C. Nasby
authors to provide their documentation as sgml, and > then have the doc build process loop in each contrib module as an appendix > inside the official docs? Can't we just copy the text files over somewhere? Actually, there was talk of improving the way that the contrib installs handled

Re: [DOCS] Get docs for contrib on the web somewhere

2006-03-17 Thread Jim C. Nasby
On Wed, Mar 08, 2006 at 02:05:44PM -0800, David Fetter wrote: > On Wed, Mar 08, 2006 at 01:50:47PM -0600, Jim C. Nasby wrote: > > It would be nice if there was an easy place to see the documentation > > for the various contrib projects. Would this be hard to setup? I > >

[DOCS] Get docs for contrib on the web somewhere

2006-03-08 Thread Jim C. Nasby
It would be nice if there was an easy place to see the documentation for the various contrib projects. Would this be hard to setup? I think the plain text would be fine, just need to post the readme's somewhere and link to them. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROT

Re: [DOCS] [GENERAL] Error correction to FAQ

2006-02-23 Thread Jim C. Nasby
I visit a mosque, I show my respect by taking off my shoes. I follow > the customs, just as I do in a church, synagogue or other holy place. But if > a believer demands that I, as a nonbeliever, observe his taboos in the > public domain, he is not asking for my respect, but for my submiss

Re: [DOCS] [PATCHES] Summary table trigger example race condition

2006-02-23 Thread Jim C. Nasby
On Wed, Feb 22, 2006 at 06:50:32PM -0600, Jim C. Nasby wrote: > Ok, here's some *Uber Ugly* code I hacked together to do something > similar for a potential book project. It's based loosely on docbook. Ok, no, for real this time... it's at http://jim.nasby.net/sgmlcode

Re: [DOCS] [PATCHES] Summary table trigger example race condition

2006-02-22 Thread Jim C. Nasby
On Fri, Jan 06, 2006 at 04:46:26PM +1300, Mark Kirkwood wrote: > Jim C. Nasby wrote: > >On Fri, Jan 06, 2006 at 02:00:34PM +1300, Mark Kirkwood wrote: > > > >>However, I think the actual change is not quite right - after running > > > > > >DOH! It would

Re: [DOCS] [HACKERS] Config file for psql

2006-02-19 Thread Jim C. Nasby
a libpq-based app. > .pgpass, pg_service, the environment vars, SSL behavior, maybe some > other things belong in the "for users" part. +1. Is there a docs TODO? -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6

Re: [DOCS] vacuum and routine maintenance docs

2006-01-19 Thread Jim C. Nasby
e many of it's settings require knowledge from other areas. Maybe the best way to deal with these is extensive cross-linking? IE: each postgresql.conf item (or set of items) should have a link back to whatever section explains it in detail. -- Jim C. Nasby, Sr. Engineering Consultant

Re: [DOCS] vacuum and routine maintenance docs

2006-01-19 Thread Jim C. Nasby
On Thu, Jan 19, 2006 at 06:00:36PM +0100, Peter Eisentraut wrote: > Am Donnerstag, 19. Januar 2006 02:31 schrieb Jim C. Nasby: > > Is there an easy way to get a 2-level outline out of the sgml? > > How would you define the TOC that we currently produce? Sorry, I guess what

Re: [DOCS] vacuum and routine maintenance docs

2006-01-18 Thread Jim C. Nasby
On Wed, Jan 18, 2006 at 08:19:16PM -0500, Tom Lane wrote: > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > I'm wondering if people feel this is an issue with the docs in general > > and isn't limited to just the admin stuff? > > Probably, but the

Re: [DOCS] vacuum and routine maintenance docs

2006-01-18 Thread Jim C. Nasby
hout more discussion of > objectives? I'm wondering if people feel this is an issue with the docs in general and isn't limited to just the admin stuff? I know I certainly have trouble finding things... I generally look for stuff by going to the appropriate page in the SQL syntax sect

Re: [DOCS] vacuum and routine maintenance docs

2006-01-18 Thread Jim C. Nasby
, I kinda put the horse before the cart...) I'm working on finding out if the community can use that text verbatim without attribution, but if nothing else it might provide you with some ideas. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http:/

Re: [DOCS] vacuum and routine maintenance docs

2006-01-17 Thread Jim C. Nasby
the FSM > is, with a link to the other part of the docs that discuss it. And then > having a link (possibly in both places) or two to more in depth articles > on fsm and fsm tuning. > > On Tue, 2006-01-17 at 16:49, Jim C. Nasby wrote: > > Before you 'put pen to paper

Re: [DOCS] vacuum and routine maintenance docs

2006-01-17 Thread Jim C. Nasby
ource page, because the coverage of the fsm there is > kind of light too. > > So, any advice? > > ---(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 dataty

Re: [DOCS] [HACKERS] Docs off on ILIKE indexing?

2006-01-17 Thread Jim C. Nasby
And yes, that's pretty poorly phrased - at least I didn't understand it > :-) I was going to submit a patch on this, and the best way seems to be adding a note to 'ILIKE', specifying that it will only work if there's a prefix to the pattern that isn't letters. Is

Re: [DOCS] [PERFORM] Stable function being evaluated more than once in a single query

2006-01-13 Thread Jim C. Nasby
Adding -docs... On Fri, Jan 13, 2006 at 07:27:28PM -0500, Tom Lane wrote: > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > Is the issue that the optimizer won't combine two function calls (ie: > > SELECT foo(..) ... WHERE foo(..)), or is it that sometimes it wo

Re: [DOCS] [PATCHES] Summary table trigger example race condition

2006-01-12 Thread Jim C. Nasby
On Thu, Jan 12, 2006 at 09:58:54PM +0100, Peter Eisentraut wrote: > Jim C. Nasby wrote: > > DOH! It would be good if doc/src had a better mechanism for handling > > code; one that would allow for writing the code natively (so you > > don't have to worry about trans

Re: [DOCS] [PATCHES] Summary table trigger example race condition

2006-01-10 Thread Jim C. Nasby
ed now that those who care are happy with it? -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---(end of broadcast)--

Re: [DOCS] [PATCHES] Summary table trigger example race condition

2006-01-05 Thread Jim C. Nasby
ry about translating < into < and > into >) and for unit testing the different pieces of code. Anyway, updated patch attached. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nas

Re: [DOCS] Supplemental contrib docs (was: [GENERAL] DBlink documentation)

2006-01-03 Thread Jim C. Nasby
nce? > > I think the answers are no, and yes, but I don't feel strongly about either. By {prefix} do you mean where PostgreSQL is being installed? If so, that would be highly non-standard. I think what you'd want is {prefix}/share/doc/postgresql/contrib/. -- Jim C. Nasby, Sr.

Re: [DOCS] CONSTRAINT syntax in ALTER TABLE

2006-01-03 Thread Jim C. Nasby
On Mon, Jan 02, 2006 at 09:04:50PM -0500, Bruce Momjian wrote: > Jim C. Nasby wrote: > > Maybe it's just me, but I find it annoying that the ALTER TABLE docs > > say to look at the CREATE TABLE docs for info on CONSTRAINT syntax. ISTM > > it would be much better to: &g

[DOCS] CONSTRAINT syntax in ALTER TABLE

2006-01-02 Thread Jim C. Nasby
l refer to CREATE TABLE, but at least make it link to the actual constraint section, instead of just linking to the top of the page as it does now. Would -docs accept a patch for #1 or #2? -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.c

[DOCS] Links to static and interactive docs on each page

2005-11-28 Thread Jim C. Nasby
read them' -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---(end of broadcast)--- TIP 3: H

[DOCS] [EMAIL PROTECTED]: Re: [ADMIN] ClusterDB error message]

2005-11-11 Thread Jim C. Nasby
of corrupted rows. regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster - End forwarded message - -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervas

[DOCS] Lazy vacuum space reclaiming

2005-10-14 Thread Jim C. Nasby
data in tables and indexes for future reuse. It only reclaims expired space from tables if it is at the end of the table, and no empty space is reclaimed from indexes." -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 5

Re: [DOCS] [SQL] Update timestamp on update

2005-10-13 Thread Jim C. Nasby
s the only examples in > chapter 35. There is a paragraph in there suggesting you go look at > the PL languages first, but obviously it's not getting the job done. Chapter 35 is plpgsql.. do you mean chapter 32.4? > Anybody have a better idea? What about a See Also section a

Re: [DOCS] COPY example for partial tables

2005-10-11 Thread Jim C. Nasby
On Tue, Oct 11, 2005 at 04:22:40PM -0700, David Fetter wrote: > On Tue, Oct 11, 2005 at 06:12:53PM -0500, Jim C. Nasby wrote: > > Why the vacuum? Seems a bit sever to do a vacuum of an entire database > > just because you created a temp table. > > Excess enthusiasm about

Re: [DOCS] COPY example for partial tables

2005-10-11 Thread Jim C. Nasby
country_name LIKE 'A%'; > + COPY a_list_countries TO '/usr1/proj/bray/sql/a_list_countries.copy'; > + ROLLBACK; > + VACUUM; > + > + > + > + > Here is a sample of data suitable for copying into a table from > STDIN: > > > -----

Re: [DOCS] XML and PostGreSql

2005-10-05 Thread Jim C. Nasby
PROTECTED] You might want to take a look at the docs first (http://www.postgresql.org/docs/8.0/static/index.html). -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cel

Re: [DOCS] Updated documentation for new sequence binding

2005-10-05 Thread Jim C. Nasby
e included in the item for all the other size functions brought into the backend? If not, ISTM they should at least be one after the other in the list... Finally, weren't more changes made it contrib than what's listed? Nothing's said about pg_autovacuum for example. -- Jim C. Nasby,

Re: [DOCS] Search bug

2005-08-21 Thread Jim C. Nasby
Guess we need an 'advanced search' or 'search help' link... On Sun, Aug 21, 2005 at 11:20:13AM -0400, Robert Treat wrote: > On Wednesday 17 August 2005 18:42, Jim C. Nasby wrote: > > I know this might be more www than docs, but I'm not on that list... > >

[DOCS] Search bug

2005-08-17 Thread Jim C. Nasby
esn't seem to allow escaping them. For example, search on 'pg_stat_activity current_query'. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Softwarehttp://pervasive.com512-569-9461 ---(end of broadcast)-

Re: [DOCS] Article doing a basic comparison of MySQL, Oracle, PostgreSQL

2005-08-15 Thread Jim C. Nasby
t of info that's not in that reference. In this case, I think the real issue is a matter of website design. It would be good if there was a prominent 'Getting started' link somewhere. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software

Re: [DOCS] Version information in docs

2005-03-29 Thread Jim C. Nasby
On Mon, Mar 28, 2005 at 05:52:30PM -0500, Bruce Momjian wrote: > Jim C. Nasby wrote: > > Something else that comes to mind... going back to older versions of the > > manual wouldn't be nearly as tedeous if there were links to older > > versions somewhere on the pages. May

Re: [DOCS] Version information in docs

2005-03-28 Thread Jim C. Nasby
Something else that comes to mind... going back to older versions of the manual wouldn't be nearly as tedeous if there were links to older versions somewhere on the pages. Maybe at every section header? -- Jim C. Nasby, Database Consultant [EMAIL PROTECTED] Give your computer

Re: [DOCS] Version information in docs

2005-03-27 Thread Jim C. Nasby
On Sun, Mar 27, 2005 at 08:54:22PM -0500, Tom Lane wrote: > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > ISTM it would be very useful if the docs specified what version a > > feature that would break in older versions was implemented in. The > > example th

Re: [PATCHES] [DOCS] Approximate count(*)

2005-03-27 Thread Jim C. Nasby
-(end of broadcast)--- > TIP 4: Don't 'kill -9' the postmaster > -- Jim C. Nasby, Database Consultant [EMAIL PROTECTED] Give your computer some brain candy! www.distributed.net Team #1828 Windows

[DOCS] Version information in docs

2005-03-27 Thread Jim C. Nasby
name arguments, but it doesn't mention that the feature was added in 8.0 and can not be used in prior versions. Anyone who's trying to write code that will run on multiple versions of PostgreSQL would want to know this. -- Jim C. Nasby, Database Consultant [EMAIL PROTECTED]

Re: [DOCS] Fast major-version upgrade (was: [GENERAL] postgresql 8.0 advantages)

2005-03-01 Thread Jim C. Nasby
On Mon, Feb 28, 2005 at 09:27:46PM +0100, Martijn van Oosterhout wrote: > On Mon, Feb 28, 2005 at 01:36:59PM -0600, Jim C. Nasby wrote: > > > I used a straight copy of the filesystem with running database > > > (over the net in my case) and immediately after that, > >

[DOCS] Fast major-version upgrade (was: [GENERAL] postgresql 8.0 advantages)

2005-02-28 Thread Jim C. Nasby
On Sun, Feb 27, 2005 at 09:27:41PM +0100, Tino Wildenhain wrote: > Hi, > > Am Samstag, den 26.02.2005, 15:35 -0600 schrieb Jim C. Nasby: > > On Sat, Feb 26, 2005 at 01:27:55AM -0800, Jeff Davis wrote: > > > On Fri, 2005-02-25 at 09:20 -0800, Si Chen wrote: > > &

Re: [DOCS] Array function

2004-11-02 Thread Jim C. Nasby
RAY(SELECT name FROM table WHERE id = ANY(id_array) ) that name[1] actually corresponds to id_array[1]? On Tue, Nov 02, 2004 at 02:43:42PM -0600, Jim C. Nasby wrote: > The datatypes chapter mentions nothing about ARRAY(), for starters. I'm > not suggesting that the reference is incompl

Re: [DOCS] Array function

2004-11-02 Thread Jim C. Nasby
dcast)--- > TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED] > -- Jim C. Nasby, Database Consultant [EMAIL PROTECTED] Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Lin

Re: [DOCS] Array function

2004-11-01 Thread Jim C. Nasby
tors section of > the manual. It adds a function array() to the list. > > Cheers, > D -- Jim C. Nasby, Database Consultant [EMAIL PROTECTED] Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux:

Re: [DOCS] [GENERAL] Turning a subselect into an array

2004-10-29 Thread Jim C. Nasby
Thanks again for the help. I did manage to find that after a bunch of searching in the mailing list. There should really be a portion of the docs dedicated to array handling. On Fri, Oct 29, 2004 at 10:40:57PM -0600, Michael Fuhr wrote: > On Fri, Oct 29, 2004 at 05:13:02PM -0500, Jim C. Na