Mail Delivery Failed - This mail couldn't be represented
- failed message -
mv?WBG>S9B_tH$du5PRXF2SkBS%&a>i6fkOLOGuKCt6
oJ+9)ßXT<%zaoGMU$:H%RKSüVGIAgtdCG-RkOBuzQSBbO
KK#7'nb;üC3hb48~-35FGtZC0q'JOß_Q)SnDCEFTTW%4B.b7
JrXißLf0d7bnZrK~+özp#_8_dßXxn(J2
Message has been sent as
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> Description:LIKE clause double-unescapes characters
This is not a bug, and it is documented. You can adjust the behavior
with LIKE ... ESCAPE ... if you don't like it.
regards, tom lane
The following bug has been logged online:
Bug reference: 1282
Logged by: Justin Pasher
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.2
Operating system: Debian Linux (unstable)
Description:LIKE clause double-unescapes characters
Details:
Perhaps I'm
=?iso-8859-1?Q?Bruno_Pr=E9vost?= <[EMAIL PROTECTED]> writes:
> I'm using postgres version 7.4.5 and had a problem with interval
> Here is my query :
> select '2004/10/31'::timestamptz + '1 day'::interval;
> Here is the answer :
> 10/31/2004 11:00:00 PM
If you are in a US time zone then that's th
Daylight savings time falls back an hour and
11/01/2004 00:00:00 becomes the answer you got because 10/31/2004 has 25 hours
in it. Sort of a bug in "real time" the interval was correct, but the day was
longer than the interval.
Sean
- Original Message -
From:
Bruno Prévo
On Wed, Oct 06, 2004 at 04:26:06PM -0400, Bruno Pr?vost wrote:
>
> I'm using postgres version 7.4.5 and had a problem with interval
>
> Here is my query :
> select '2004/10/31'::timestamptz + '1 day'::interval;
>
> Here is the answer :
> 10/31/2004 11:00:00 PM
I'd guess that Daylight Saving Tim
Hi,I'm using postgres version 7.4.5
and had a problem with interval
Here is my query :
select '2004/10/31'::timestamptz + '1
day'::interval;
Here is the answer :
10/31/2004 11:00:00 PM
Is it a bug or I do something wrong?
I tested my query on 3 server and have always the same
answer.
The following bug has been logged online:
Bug reference: 1281
Logged by: Thomas Reinelöv
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 Beta
Operating system: Win2000
Description:I cannot find the ODBC driver in available ODBC drivers
Details:
After i
Devrim GUNDUZ <[EMAIL PROTECTED]> writes:
> Do we still need a backported fix?
No. This is a behavioral change of a *very* longstanding behavior.
It's going in at 8.0, not 7.4.something.
regards, tom lane
---(end of broadcast)-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Wed, 6 Oct 2004, Tom Lane wrote:
Devrim GUNDUZ <[EMAIL PROTECTED]> writes:
Am I missing something, or is it a bug? I can't reproduce it in 8.0beta2.
whereas prior versions did the rollback but still reported the command
tag as COMMIT. AFAIR, Po
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> We are getting 2 errors
> 1) We get the error 'Unexpected EOF at Client Connection' and appplication
> stops responding. This error is shown in the postgres logs.
> 2) At times we get the message 'Apache Tomcat Stopped' on the web server and
Devrim GUNDUZ <[EMAIL PROTECTED]> writes:
> Am I missing something, or is it a bug? I can't reproduce it in 8.0beta2.
8.0 actually behaves the same way: the COMMIT gets you out of the
transaction block. It just tells you that it's treating it as a
rollback:
regression=# comm;
ERROR: syntax erro
On Wed, 6 Oct 2004, Devrim GUNDUZ wrote:
> [I say COMMIT on a failed transaction and it looks successful, but isn't.]
This is a long standing behavior. Internally a ROLLBACK happens, but
commit is reported back to the client. This has only changed in 8.0 to
reflect what actually happened.
The following bug has been logged online:
Bug reference: 1280
Logged by: Shilpa Upadhye
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.5
Operating system: freebsd 5.1
Description:Unexpected EOF at Client Connection
Details:
Hi,
Our database configura
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm using 7.4.5 on a test platform and had a weird behaviour. Here is the
case:
test=# CREATE TABLE t1 (s_no int2 PRIMARY KEY,a varchar(10));
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "t1_pkey"
for table "t1"
test=# CREATE TA
15 matches
Mail list logo