select * from table where field ILIKE 'blAH'; -- ;-)
is almost as easy :-)
PS: no, don't do this if you want portability. I think the charset
idea's a better one.
Ron
select * from table where lower(field)=lower('BLah') will break
portability too in the sense that many DBs (perhaps all
Why not a cast?
template1=# select current_timestamp::time;
time
-
11:24:22.004207
(1 row)
template1=# select current_timestamp::time(0);
time
--
11:24:26
(1 row)
--- Christopher Kings-Lynne [EMAIL PROTECTED] wrote:
phd=# select time(abstime(timestamp
Hi all
I have read some code on transaction part.
When the new transaction starts, it record the snapshot of database containing the
current transaction id,etc. So depending on the snapshot
, the transaction decide which tuple is visible.
But transaction could also be implemented by lock. so I am
Dear PostgreSQL hackers,
I am developing a disk IO scheduler for Linux and am aiming to
have it included in the stable 2.6 release. Due to its design,
performance regressions do appear, and are often more specific
to the workload in question than with other schedulers, hence
one has to go beyond
Ok, I was a good boy and tried -interfaces first. No answer.
I'm trying to get a functioning version of plpython on FreeBSD, while
using python from the ports system.
The problem is that the ports system build python with thread
support. postmaster doesn't have thread support, so when the
On Mon, Mar 17, 2003 at 11:23:47AM -0600, Taral wrote:
Yes, that's exactly it. It's an index _scan_. It should simply be able
to read the maximum straight from the btree.
Still doesn't work, even with rewritten query. It sort a
Limit(Sort(Index Scan)), with 1333 rows being pulled from the
Joe Conway wrote:
Jason Earl wrote:
Actually, I think it was someone else (Joe???) that is doing the leg
work, and he was the one choosing explode / implode and getting
gruff for it, so I was just stepping in and defending his decision.
Oops, my bad. My brain must already think that it is
Hi,
I would appreciate it if you could give me a suggestion
for a not-too-difficult to set up or interpret PostgreSQL
benchmark with a reasonable running time ( an hour or so)
which I can add to my performance regression tests.
Check out `make check', a regression test which ships with
Tom Lane wrote:
It was mostly meant as a broad hint not to write open() failed, which
can clearly be written more user-friendly without loss of information.
For less obvious cases we can use a mixed style. Say 'could not
synchronize file %s with disk (fsync failed)'. That tells people at
Gavin Sherry wrote:
Hi,
I would appreciate it if you could give me a suggestion
for a not-too-difficult to set up or interpret PostgreSQL
benchmark with a reasonable running time ( an hour or so)
which I can add to my performance regression tests.
Check out `make check', a regression
Just making sure that posts make it through after upgrading perl and
installing some anti-spam software ... ignore ..
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Thank you, Bruce for info.
Best regards
Rony
- Original Message -
From: Bruce Momjian [EMAIL PROTECTED]
To: Ronald Kuczek [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, March 19, 2003 3:34 PM
Subject: Re: [HACKERS] Win32 native port
I will start working on it next week.
On Tue, 2003-03-18 at 19:00, Hiroshi Inoue wrote:
Bruce Momjian wrote:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
The question here is do we want to offer a half-baked solution,
recognizing that it's some improvement over no solution at all?
Or do we feel it
13 matches
Mail list logo
