Re: [HACKERS] psql SET/RESET/SHOW tab completion
On 13 Aug 2005 21:42:45 -0400, Greg Stark [EMAIL PROTECTED] wrote: Tom Lane [EMAIL PROTECTED] writes: However, if you favor a no thought required approach, listing 'em all is certainly the path of least resistance. I'm just dubious that that maximizes the usefulness of tab completion. I'm not sure if you're interested, but my 2c speaking as a user would be for tab completion to include all variables. I often hit tab completion in new programs just to find out what's out there and would take something missing to be positive proof it didn't exist. Oh, I usually do the same thing. I guess my approach could summarized as: I assume tab-completion is not too smart -- it just completes one of valid values. And at the times where tab-completion is smart, it is smart and configurable -- as ZSH tab-completion. And were PostgreSQL's tab-completion go the smart way I would be for adding a GUC which allowed to fine-grain what it actually gives (all variables, settable variables, 'vacuum%' and 'enable%' variables, etc. ;))). Regards, Dawid ---(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: [HACKERS] SPARQL
Am Donnerstag, 11. August 2005 04:33 schrieb Christopher Kings-Lynne: Looks like there's a standard XML way of returning query results: http://www.w3.org/TR/2005/WD-rdf-sparql-XMLres-20050801/ This is for RDF queries, not for SQL queries. For SQL, the SQL/XML standard gives you a standard XML format for table representation. I have some code for that if anyone is interested. I will put that up on pgFoundry one of these days. ---(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: [HACKERS] psql SET/RESET/SHOW tab completion
Greg Stark [EMAIL PROTECTED] writes: I'm not sure if you're interested, but my 2c speaking as a user would be for tab completion to include all variables. OK, I'm clearly outvoted on this one. How about we make SHOW tab-complete everything listed in pg_settings, while SET/RESET tab-complete everything that's USERSET or SUSET? (We could probably even make it suppress SUSET if you aren't superuser, but I'm not sure if that's worth the trouble.) regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] Simplifying wal_sync_method
UFS was the filesystem on the Solaris 9 box. -- Thomas F. O'Connell Co-Founder, Information Architect Sitening, LLC Strategic Open Source: Open Your i™ http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) On Aug 11, 2005, at 4:18 PM, Andrew Sullivan wrote: On Wed, Aug 10, 2005 at 02:11:48AM -0500, Thomas F. O'Connell wrote: I was recently witness to a benchmark of 7.4.5 on Solaris 9 wherein it was apparently demonstrated that fsync was the fastest option among the 7.4.x wal_sync_method options. If there's a way to make this information more useful by providing more data, please let me know, and I'll see what I can do. What would be really interesting to me to know is what Sun did between 8 and 9 to make that so. We don't use Solaris for databases any more, but fsync was a lot slower than whatever we ended up using on 8. I wouldn't be surprised if they'd wired fsync directly to something else; but I can hardly believe it'd be faster than any other option. (Mind, we were using Veritas filesyste with this, as well, which was at least half the headache.) A ---(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: [HACKERS] small proposal: pg_config record flag variables?
Am Dienstag, 9. August 2005 20:49 schrieb Tom Lane: Currently, pg_config will tell about the configure options that were used, but it does not let you find out if any environment variables were used to determine CC, CFLAGS, etc. If you put these flags onto the configure command line, then they are recorded. E.g.: $ ./pg_config --configure '--prefix=/home/peter/devel/pg81/pg-install' 'CFLAGS=-W' This is good for reproducing the build. If you really want to know everything about the build environment, then you should look into config.log. We shouldn't install config.log by default because it contains information that you might not want to publish, but it's the place to look at for diagnosing the build environment. ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] small proposal: pg_config record flag variables?
Peter Eisentraut [EMAIL PROTECTED] writes: Am Dienstag, 9. August 2005 20:49 schrieb Tom Lane: Currently, pg_config will tell about the configure options that were used, but it does not let you find out if any environment variables were used to determine CC, CFLAGS, etc. If you put these flags onto the configure command line, then they are recorded. E.g.: $ ./pg_config --configure '--prefix=/home/peter/devel/pg81/pg-install' 'CFLAGS=-W' Sure, but people frequently do not do it that way. The point of my proposal was to make sure we could find out the flags actually used after-the-fact, whether or not config.log is still around. regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] SPARQL
This is for RDF queries, not for SQL queries. For SQL, the SQL/XML standard gives you a standard XML format for table representation. I have some code for that if anyone is interested. I will put that up on pgFoundry one of these days. I'm interested in the SQL format so that I can implement it in phpPgAdmin - can you give me an example, or docs on it? Chris ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] psql SET/RESET/SHOW tab completion
Tom Lane wrote: Greg Stark [EMAIL PROTECTED] writes: I'm not sure if you're interested, but my 2c speaking as a user would be for tab completion to include all variables. OK, I'm clearly outvoted on this one. How about we make SHOW tab-complete everything listed in pg_settings, while SET/RESET tab-complete everything that's USERSET or SUSET? (We could probably even make it suppress SUSET if you aren't superuser, but I'm not sure if that's worth the trouble.) Yea, that's what I was thinking. Not sure if the superuser check is _too_ smart. -- Bruce Momjian| http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(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: [HACKERS] SPARQL
On Mon, Aug 15, 2005 at 09:53:18AM +0800, Christopher Kings-Lynne wrote: This is for RDF queries, not for SQL queries. For SQL, the SQL/XML standard gives you a standard XML format for table representation. I have some code for that if anyone is interested. I will put that up on pgFoundry one of these days. I'm interested in the SQL format so that I can implement it in phpPgAdmin - can you give me an example, or docs on it? It's in 5WD-14-XML-2003-09.pdf which is available at http://wiscorp.com/SQLStandards.html Cheers, D -- David Fetter [EMAIL PROTECTED] http://fetter.org/ phone: +1 510 893 6100 mobile: +1 415 235 3778 Remember to vote! ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
