Re: [ADMIN] date out of range for timestamp

2010-12-28 Thread Tom Lane
David Rericha writes: > Thanks, Tom. That was it. After I ran analyze on the table, the error > disappeared. Yeah, I just duplicated the failure here. It only happens if the comparison value falls into the histogram bucket adjoining the out-of-range value, which is why you didn't see it happen

Re: [ADMIN] date out of range for timestamp

2010-12-28 Thread David Rericha
Thanks, Tom. That was it. After I ran analyze on the table, the error disappeared. David J. Rericha OSS, LLC Projects Manager 563-650-5446 On 12/28/2010 08:45 PM, Tom Lane wrote: > [ please keep the list cc'd ] > > David Rericha writes: > >> I am truly typing the date as a literal. It tur

Re: [ADMIN] date out of range for timestamp

2010-12-28 Thread Tom Lane
[ please keep the list cc'd ] David Rericha writes: > I am truly typing the date as a literal. It turned out that I did have > a date of year 201, which would have been out of range, but I > changed it. But I still get the error. Hmm. Try re-running ANALYZE on the table. I'm thinking tha

Re: [ADMIN] date out of range for timestamp

2010-12-28 Thread Tom Lane
David Rericha writes: > I have a 21 GB database in version 8.4.5 that is giving me a curious > error when I perform a query on one of the tables: > select count(*) from moms_outside_report where outreport_date <= > '12/10/2010'; > ERROR: date out of range for timestamp Did you really truly type

Re: [ADMIN] date out of range for timestamp

2010-12-28 Thread Scott Marlowe
On Tue, Dec 28, 2010 at 5:02 PM, David Rericha wrote: > select count(*) from moms_outside_report where outreport_date <= > '12/10/2010'; > ERROR:  date out of range for timestamp Try using an ISO date: select count(*) from moms_outside_report where outreport_date <= '2010-12-10'; I wonder if yo

[ADMIN] date out of range for timestamp

2010-12-28 Thread David Rericha
Dear postgresql.org members: I have a 21 GB database in version 8.4.5 that is giving me a curious error when I perform a query on one of the tables: Table "public.moms_outside_report" Column |Type | Modifiers -

Re: [ADMIN] Postgre installation issue

2010-12-28 Thread Scott Marlowe
On Tue, Dec 28, 2010 at 8:41 AM, Lou Picciano wrote: > But Dusan, > I don't think you can have a user see _only_ his own databases, can you? I > think all can see all databases, if I'm not mistaken, even if they cannot > connect to all. (Someone here will correct me, I'm sure!)  Lou Correct. --

Re: [ADMIN] Postgre installation issue

2010-12-28 Thread Lou Picciano
But Dusan, I don't think you can have a user see _only_ his own databases, can you? I think all can see all databases, if I'm not mistaken, even if they cannot connect to all. (Someone here will correct me, I'm sure!) Lou - Original Message - From: "Dusan Misic" To: "ammar fallah

Re: [ADMIN] Postgre installation issue

2010-12-28 Thread Dusan Misic
Oops, I gave wrong answer. Sorry :-) On Tue, Dec 28, 2010 at 12:54 PM, Dusan Misic wrote: > Check if Secondary logon service is running. If it is not running, start it > and try again to start PostgreSQL. It should work now. > > > On Tue, Dec 28, 2010 at 8:33 AM, Ammar Fallaha < > ammar.fall...@

Re: [ADMIN] Postgre installation issue

2010-12-28 Thread Dusan Misic
Check if Secondary logon service is running. If it is not running, start it and try again to start PostgreSQL. It should work now. On Tue, Dec 28, 2010 at 8:33 AM, Ammar Fallaha wrote: > We are trying to switch from Oracle 10g to Postgre but I am having few > technical issues which I am listing