Harvell F wrote:
Getting back to the original posting, as I remember it, the question
was about seldom changed information. In that case, and assuming a
repetitive query as above, a simple query results cache that is keyed on
the passed SQL statement string and that simply returns the
On Sun, Oct 15, 2006 at 06:33:36PM -0700, Jeremy Drake wrote:
2) When updating a PostgreSQL record, I updated the memcache record
to the new value. If another process comes along in parallel before
I commit, that is still looking at an older view, cross-referencing
On Mon, Oct 16, 2006 at 05:59:05PM +0930, Shane Ambler wrote:
Registering each cache entry by the tables included in the query and
invalidating the cache during on a committed update or insert
transaction to any of the tables would, transparently, solve the
consistency problem.
That was
On Saturday 14 October 2006 19:48, Tom Lane wrote:
Sean Davis [EMAIL PROTECTED] writes:
Trying to build 8.2beta1 on MacOS G5 Xserver, OS version 10.4.7. I got
this:
/usr/bin/libtool: for architecture: cputype (16777234) cpusubtype (0)
file: -lSystem is not an object file (not allowed in
Hi, Shane,
Shane Ambler wrote:
CREATE TABLESPACE myramcache LOCATION MEMORY(2GB);
It's already possible to do this, just create the TABLESPACE in a
ramdisk / tmpfs or whatever is available for your OS.
HTH,
Markus
--
Markus Schaber | Logical TrackingTracing International AG
Dipl. Inf. |
Hi, Ashish,
Ashish Goel wrote:
But the same code worked when I inserted around 2500 images in the
database. After that it started crashing.
Testing can never prove that there are no bugs.
It's like the proof that all odd numbers above 1 are prime:
3 is prime, 5 is prime, 7 is prime, so I
On 10/16/06, Bruce Momjian [EMAIL PROTECTED] wrote:
Jim C. Nasby wrote:
On Sun, Oct 15, 2006 at 06:19:12PM -0400, Tom Lane wrote:
I suspect the problem here is that the backend isn't linked with
-lpthread. We aren't going to let libpython dictate whether we do so,
either...
Fix config
On 10/12/06, Tom Lane [EMAIL PROTECTED] wrote:
Weslee Bilodeau [EMAIL PROTECTED] writes:
It works perfectly so long as I used the same key for all my custom
types. When I want a different key for each type though (so for example,
encrypt credit cards with one key, addresses with another, etc)
On 10/15/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Using memcache, I've had problems with consistency brought right to
the front. Both of these have failed me:
1) When updating a PostgreSQL record, I invalidate the memcache record.
If another process comes along in parallel
On Sun, Oct 15, 2006 at 06:15:27PM -0400, Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
I am also wondering, now that it's been raised, if we need to issue a use
utf8; in the startup code, so that literals in the code get the right
encoding.
Good question. I took care to
Martijn van Oosterhout kleptog@svana.org writes:
It's clear whether you actually want to allow people to put utf8
characters directly into their source (especially if the database is
not in utf8 encoding anyway). There is always the \u{} escape.
Well, if the database encoding isn't utf8
On 16 Oct 2006, at 4:29, Shane Ambler wrote:
Harvell F wrote:
Getting back to the original posting, as I remember it, the
question was about seldom changed information. In that case, and
assuming a repetitive query as above, a simple query results cache
that is keyed on the passed
On Mon, 2006-10-16 at 13:59 +0200, Markus Schaber wrote:
It's already possible to do this, just create the TABLESPACE in a
ramdisk / tmpfs or whatever is available for your OS.
This is not an ideal solution: if the machine reboots, the content of
the tablespace will disappear, requiring manual
Marko Kreen wrote:
On 10/16/06, Bruce Momjian [EMAIL PROTECTED] wrote:
Jim C. Nasby wrote:
On Sun, Oct 15, 2006 at 06:19:12PM -0400, Tom Lane wrote:
I suspect the problem here is that the backend isn't linked
with -lpthread. We aren't going to let libpython dictate
whether we do
Since installing python 2.5, tapir has been failing:
http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=tapirdt=2006-10-15%2020:20:16
Several of the failures appear to be a simple change in error reporting;
I haven't investigated why import_succeed() failed.
Should python 2.5 work with plpython?
--
Marko Kreen wrote:
On 10/12/06, Tom Lane [EMAIL PROTECTED] wrote:
Weslee Bilodeau [EMAIL PROTECTED] writes:
It works perfectly so long as I used the same key for all my custom
types. When I want a different key for each type though (so for
example,
encrypt credit cards with one key,
On Mon, Oct 16, 2006 at 12:40:44PM -0400, Neil Conway wrote:
On Mon, 2006-10-16 at 13:59 +0200, Markus Schaber wrote:
It's already possible to do this, just create the TABLESPACE in a
ramdisk / tmpfs or whatever is available for your OS.
This is not an ideal solution: if the machine reboots,
Jim C. Nasby wrote:
Since installing python 2.5, tapir has been failing:
I have removed the use of the deprecated whrandom module, which should
take care of one regression test failure, but after that I get
*** glibc detected *** free(): invalid pointer: 0xa5df6e78 ***
LOG: server process
While trying to clean up ParseDateTime so it works reliably with full
timezone names, I found out about a feature that so far as I can tell
has never been documented except in comments in datetime.c. The
datetime input code tries to recognize what it calls POSIX time zones,
which are timezone
What about time zones like Tehran (GMT+3:30), Kabul (GMT+4:30), Katmandu
(GMT+5:45) and other non-cardinal-hour GMT offsets? Is this handled in
some *documented* way already?
--
Brandon Aiken
CS/IT Systems Engineer
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Brandon Aiken [EMAIL PROTECTED] writes:
What about time zones like Tehran (GMT+3:30), Kabul (GMT+4:30), Katmandu
(GMT+5:45) and other non-cardinal-hour GMT offsets? Is this handled in
some *documented* way already?
Sure. This has worked since PG 7.2 or so:
regression=# select '12:34:00
On Mon, 16 Oct 2006, [EMAIL PROTECTED] wrote:
On Sun, Oct 15, 2006 at 06:33:36PM -0700, Jeremy Drake wrote:
2) When updating a PostgreSQL record, I updated the memcache record
to the new value. If another process comes along in parallel before
I commit, that is still
I wrote:
... I'm not entirely convinced that it really is a POSIX-sanctioned
notation, either --- the POSIX syntax the zic code knows about is
different.
Actually, I take that back: it is a subset of the same notation, but
the datetime.c code is misinterpreting the spec!
The POSIX timezone
-Original Message-
I think we had that problem solved too in principle: build the new
catalogs in a new $PGDATA directory alongside the old one, and hard-link
the old user table files into that directory as you go. Then pg_upgrade
never needs to change the old directory tree at all.
24 matches
Mail list logo
