By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
464,789 Members | 1,432 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 464,789 IT Pros & Developers. It's quick & easy.

CURRENT_TIMESTAMP causes Postgres to shutdown connection

P: n/a

We've been working to try and solve this issue. On PostgreSQL
install(running on RH 7.1), we can't get CURRENT_TIMESTAMP,
CURRENT_TIME, or now() to function. All the results is psql reporting
the server closed the connection.

I've been searching all over for clues about this, and haven't found a
thing. If anyone has an idea as to the source of this, that would be

Nov 11 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.