[GENERAL] make check fails on OS X 10.6.2

2009-12-16 Thread Tim Hart
All, I've been installing postgres from source on os x for years, but I haven't generally run 'make check' before I install. I don't feel that running 'make check' is terribly necessary in this case - it's a personal sandbox on my laptop, with no production value. Regardless, I realize that

Re: [GENERAL] make check fails on OS X 10.6.2

2009-12-16 Thread Tim Hart
live instance, reran 'make check', and make check passed. Thanks for the pointers. Tim Hart Software Consultant 615-713-9956 :cell tjhart :AIM th...@me.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org

Re: [GENERAL] PQstatus does not seem to work

2009-08-10 Thread Tim Hart
On 8/10/09 12:08 PM, Sam Mason s...@samason.me.uk wrote: On Tue, Aug 11, 2009 at 12:41:47AM +0800, Juan Backson wrote: I used PQstatus(conn) function to check connection status, but I found that it still returns CONNECTION_OK even after postgres is restarted. Does anyone know if there is

[GENERAL] Unexpected behavior from psql

2009-01-11 Thread Tim Hart
This is a minor issue. Not really a problem for me at the moment, but I wanted to understand if it was intended: tjhart=# \d No relations found. tjhart=# \dn List of schemas Name| Owner +-- information_schema | postgres pg_catalog

Re: [GENERAL] Unexpected behavior from psql

2009-01-11 Thread Tim Hart
On Jan 11, 2009, at 4:41 PM, Jeff Davis wrote: On Sun, 2009-01-11 at 15:33 -0600, Tim Hart wrote: tjhart=# set search_path to foo, public; SET tjhart=# \d List of relations Schema | Name| Type | Owner +---+---+ foo| bar_table | table | tjhart

Re: [GENERAL] Unexpected behavior from psql

2009-01-11 Thread Tim Hart
On Jan 11, 2009, at 8:16 PM, Jeff Davis wrote: On Sun, 2009-01-11 at 17:13 -0600, Tim Hart wrote: Would it be worthwhile to specify this in the documentation? One of the sources of my confusion was the following statement: http://www.postgresql.org/docs/8.3/interactive/app-psql.html

[GENERAL] General subselect question

2009-01-05 Thread Tim Hart
duplication of code for me on the second case) and decide (assuming I'm still motivated on Friday ;) ). But in the general case, do I have to pay special attention with unions in subselects? Tim Hart 615-713-9956 :cell timothyjhart :Y! tjh...@me.com :AIM -- Sent via pgsql-general mailing

[GENERAL] Question about the enum type

2008-02-17 Thread Tim Hart
the name of the enum to fielding_position for clarity's sake anyway. But for my own education - what's so unique about the name 'position'? Tim Hart ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate

[GENERAL] Fwd: Question about the enum type

2008-02-17 Thread Tim Hart
message: From: Tim Hart [EMAIL PROTECTED] Date: February 17, 2008 8:24:44 PM CST To: pgsql-general@postgresql.org Subject: Question about the enum type I was playing around with the enum type today. I was toying around with a schema to model information about baseball, and decided to create

Re: [GENERAL] Question about the enum type

2008-02-17 Thread Tim Hart
that. What I didn't state in that e-mail was that I tried to create an enum type that was another name in the list which was non-reserved (cannot be function or type). In that case, I did see the automatic quoting behavior I saw with position. Thanks for the prompt reply. Tim Hart

Re: [GENERAL] Question about the enum type

2008-02-17 Thread Tim Hart
On Feb 17, 2008, at 11:21 PM, Tom Lane wrote: The reason position is special is that the SQL spec calls out weird specialized syntax for it: Given the spec, I completely understand. Given the roundabout way I discovered the nature of the problem, I'm curious: At the time I executed the

Re: [GENERAL] Question about the enum type

2008-02-17 Thread Tim Hart
On Feb 18, 2008, at 12:10 AM, Tom Lane wrote: Would it have been reasonable to expect some kind of notice or warning message stating that 'position' was special, and double-quotepositiondouble-quote would be used instead? The way you phrase that makes me think you misunderstand what's

Re: [GENERAL] Is there a way to run tables in RAM?

2006-07-13 Thread Tim Hart
I cant say for certain from the detail youve given, but partial indexes may be an acceptable solution to your problem. http://www.postgresql.org/docs/8.1/interactive/indexes-partial.html From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roy Souther Sent:

Re: [GENERAL] Long term database archival

2006-07-12 Thread Tim Hart
Wouldn't you run into driver problems if you tried to restore a 20 year old image? After all, you probably won't be using the same hardware in 20 years... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jan Wieck Sent: Wednesday, July 12, 2006 9:26 AM To:

Re: [GENERAL] doesn't recognize !=- (not equal to a negative value)

2006-07-11 Thread Tim Hart
From a brief and similar session (below), perhaps the best solution is to simply insert a space between the '=' and the '-'?? Welcome to psql 8.1.4, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help with psql

Re: [GENERAL] User privileges in web database applications

2006-06-29 Thread Tim Hart
I'm coming in a bit late to this conversation, so forgive me if I've missed something. Isn't this problem the reason that connection pools were created? In a connection pool, connections are only associated with a particular user for the duration of a transaction. Once the transaction is

Re: [GENERAL] Null and Void() - Or, Abandon All Hope Ye Who allow

2006-06-28 Thread Tim Hart
This reminds me of my favorite Bertrand Russell quote: The difference between theory and practice is: in theory there is no difference, but in practice, there is -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Florian G. Pflug Sent: Wednesday, June 28,

Re: [GENERAL] Any *real* reason to choose a natural, composite PK over a surrogate, simple PK?

2006-06-08 Thread Tim Hart
While this statement is accurate, it isn't very precise. Needs change. Requirements change. Usage changes. Any one of these changes can invalidate a very correct initial analysis. A wise designer anticipates change to minimize impact on both current work *and* future development effort.

[GENERAL] What are the characteristics of a good user-defined data type?

2006-06-07 Thread Tim Hart
? Tim Hart

Re: [GENERAL] What are the characteristics of a good user-defined data type?

2006-06-07 Thread Tim Hart
for. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane Sent: Wednesday, June 07, 2006 9:37 AM To: Tim Hart Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] What are the characteristics of a good user-defined data type? Tim Hart [EMAIL PROTECTED] writes

[GENERAL] Evaluating client processes vs stored procedures

2006-04-12 Thread Tim Hart
List, I have a client process that is causing some performance issues with my app. On my current platform, the standard automated profiling tools are not available. Consequently, I can't easily determine where the bottleneck is in the process. I have an inkling that rewriting the client

[GENERAL] Seeking comments on schema design and data integrity

2006-02-11 Thread Tim Hart
the database. All opinions on this are welcome. Tim Hart Senior Java/J2EE developer [EMAIL PROTECTED] :email (312)560-4267 :phone ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org