-Original Message-
Peter Eisentraut [EMAIL PROTECTED] writes:
* MySQL is used as a primary development platform.
Another good reason.
Actually that's *the* reason --- it's always going to be hard for
Postgres to look good for an application that's been
designed/optimized
for
you could store the pkey as a md5 or sha1
of the image's data. or any of the other large hashing algorithms.
that way your index only has to compare 32 or 40 bytes instead of kilobytes per
row.
as for the main color, you could generate histogram-like
columns (or even a single column)
Volkan YAZICI wrote:
On Jul 20 08:21, Dan Strömberg wrote:
I would like to know if it is possible to find out the datatypes in the
resultset of a query or a set returning
function without actually executing them ?
As Tom mentioned, there's support for this feature in the protocol
level, but
Martijn van Oosterhout wrote:
On Fri, Jul 21, 2006 at 04:14:52PM +0300, Volkan YAZICI wrote:
On Jul 21 09:02, Jacob Coby wrote:
Volkan YAZICI wrote:
As Tom mentioned, there's support for this feature in the protocol
level, but I don't know any API supports this yet. However, here's a
patch
badlydrawnbhoy wrote:
Hi all,
I've got a database of URLs, and when inserting new data into it I want
to make sure that there are no functionally equivalent URLs already
present. For example, 'umist.ac.uk' is functionally the same as
'umist.ac.uk/'.
I find that searching for the latter form,
Tom Lane wrote:
Jacob Coby [EMAIL PROTECTED] writes:
I then tried:
foo=# select * from pg_catalog.pg_statistic ;
ERROR: could not access status of transaction 3242180415
DETAIL: could not open file pg_clog/0C13: No such file or directory
so it seems that pg_catalog.pg_statistic has somehow
,
--
Jacob Coby
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Tom Lane wrote:
Jacob Coby [EMAIL PROTECTED] writes:
I've got a pg 8.1.1 server running autovacuum, and it started attempting
to vacuum template0.
2006-06-22 15:00:50 EDT LOG: autovacuum: processing database template0
2006-06-22 15:00:50 EDT ERROR: could not access status of transaction
We recently upgraded from php 4.3.10 to 5.1.2, and the %system time has
skyrocketed:
Cpu(s): 42.8% us, 43.6% sy, 0.0% ni, 11.3% id, 2.2% wa, 0.2% hi, 0.0% si
Mem: 8312844k total, 7566168k used, 746676k free,22356k buffers
Swap: 2040244k total, 520k used, 2039724k free,
Bill Moran wrote:
On Tue, 06 Jun 2006 09:19:10 -0400
Jacob Coby [EMAIL PROTECTED] wrote:
We recently upgraded from php 4.3.10 to 5.1.2, and the %system time has
skyrocketed:
Cpu(s): 42.8% us, 43.6% sy, 0.0% ni, 11.3% id, 2.2% wa, 0.2% hi, 0.0% si
Mem: 8312844k total, 7566168k used
10 matches
Mail list logo