The following bug has been logged online:
Bug reference: 1176
Logged by: thoyyib
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: linux
Description:PHP connection
Details:
The error report is :
FATEL: IDENT authentication failed for us
On Tue, 2004-06-22 at 10:29, PostgreSQL Bugs List wrote:
...
> Description:PHP connection
>
> Details:
>
> The error report is :
> FATEL: IDENT authentication failed for user "postgres"
> I am a new user. pls help me
You must ensure that the authentication options are set correctly
PostgreSQL Bugs List wrote:
Description:PHP connection
Details:
The error report is :
FATEL: IDENT authentication failed for user "postgres"
I am a new user. pls help me
You should update the access permissions in you pg_hba.conf file.
Details are in the manuals.
I recommend you sub
The following bug has been logged online:
Bug reference: 1177
Logged by: Jan Normann Nielsen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Linux (Insignificant)
Description:JDBC driver doesn't handle all dates correctly
Details:
In
On Tue, Jun 22, 2004 at 06:29:29 -0300,
PostgreSQL Bugs List <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
This isn't really a bug; you should have posted you question to pgsql-novice.
(Followups set to there and to you.)
>
> Bug reference: 1176
> Logged by:
The following bug has been logged online:
Bug reference: 1178
Logged by: Theo Kramer
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Redhat Linux 9
Description:PQexecPrepared - PostgreSQL 7.4.1
Details:
I am having a problem with PQex
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> PQexec(conn,
>"PREPARE S123_000 (text) AS SELECT * from test1 WHERE t = $1");
> When invoking PQexecPrepared() I get the following message from the backend
> ERROR: prepared statement "S123_" does not exist
Case sensitivity. P
The following bug has been logged online:
Bug reference: 1179
Logged by: Mauricio CASTRO ESPINOSA
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.2.4
Operating system: RedHat 7.3 uname:Linux Play 2.4.18-3 #1 Thu Apr 18
07:37:53 EDT 2002 i686 unknown
Description:
On Tue, 22 Jun 2004, PostgreSQL Bugs List wrote:
> must_betrue is false for the query bellow
One of those is a bigint, the other is a double expression that is
probably very slightly different from the integer you're comparing it to.
What is the result of the date_part(...)-time?
--
On Tue, 22 Jun 2004, Mauricio CASTRO wrote:
> You are right!
>
> I am doing something wrong? I understand that there is a difference but I
> don't know why.
Floating point math is inexact. The date_part(...) is returning a value
that is very close to, but not exactly 4.031 due to accuracy limita
On Tue, 22 Jun 2004, PostgreSQL Bugs List wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1177
> Logged by: Jan Normann Nielsen
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 7.4
> Description:JDBC driver doesn't handle all dates cor
The following bug has been logged online:
Bug reference: 1180
Logged by: Ben Bidner
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.3.2
Operating system: linux 2.4.20
Description:incorrect date handling
Details:
colony=# CREATE TABLE foo (dtime TIMESTAMP
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> PostgreSQL version: 7.3.2
> colony=# insert into foo values ('2003-12-11 23:59:60.00');
> ERROR: Bad timestamp external representation '2003-12-11 23:59:60.00'
Use a more recent PG version ... we have fixed a thing or two since
7.3 (in fact 7.
On Tue, 22 Jun 2004, Tom Lane wrote:
> "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> > PostgreSQL version: 7.3.2
>
> > colony=# insert into foo values ('2003-12-11 23:59:60.00');
> > ERROR: Bad timestamp external representation '2003-12-11 23:59:60.00'
>
> Use a more recent PG version ...
14 matches
Mail list logo