Tom Lane wrote:
Having seen a couple recent reports of could not access status of
transaction for old, not-obviously-corrupt transaction numbers, I went
looking to see if I could find a way that the system could truncate CLOG
before it's really marked all occurrences of old transaction numbers as
Dear Sirs,
I would like to know if there are any discussions about
creating an embedded version on postgresql. My thoughts
go towards building/porting a sqlite equivalent of pg.
Regards,
GB.
---(end of broadcast)---
TIP 1: subscribe and
create index people_male_gay_ix on people (city) where gender = 'male' and
orientation = 'gay';
You've forgotten part of my premise (based on a real case I discussed on IRC)
that there are EIGHTEEN criteria columns.
That is why I said maybe :-) Whether it helps depends on the number of
[EMAIL PROTECTED] wrote:
I would like to know if there are any discussions about
creating an embedded version on postgresql. My thoughts
go towards building/porting a sqlite equivalent of pg.
Yes, there have been several. Peruse the archives:
http://archives.postgresql.org/
--
dave
On Wed, Oct 13, 2004 at 12:18:08PM -0400, Tom Lane wrote:
I think what we ought to do to solve this problem permanently is to stop
making the callers of the HeapTupleSatisfiesFoo() routines responsible
for checking for hint bit updates. It would be a lot safer, and AFAICS
not noticeably less
It has just been brought to my attention that we are being very
restrictive about what we allow to be done in trusted plperl. Basically
we allow the :default and :base_math set of operations (run perldoc
Opcode or see http://www.perldoc.com/perl5.8.0/lib/Opcode.html for
details of what these
Added to TODO:
* Prevent inet cast to cidr if the unmasked bits are not zero, or
zero bits
---
Andrew Dunstan wrote:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Not sure how
On Thu, 14 Oct 2004, Andrew Dunstan wrote:
It has just been brought to my attention that we are being very
restrictive about what we allow to be done in trusted plperl. Basically
we allow the :default and :base_math set of operations (run perldoc
Opcode or see
Jon Jensen wrote:
On Thu, 14 Oct 2004, Andrew Dunstan wrote:
It has just been brought to my attention that we are being very
restrictive about what we allow to be done in trusted plperl. Basically
we allow the :default and :base_math set of operations (run perldoc
Opcode or see
On 14. okt 2004, at 21:09, Andrew Dunstan wrote:
It has just been brought to my attention that we are being very
restrictive about what we allow to be done in trusted plperl.
Basically we allow the :default and :base_math set of operations (run
perldoc Opcode or see
On Thu, 14 Oct 2004, Andrew Dunstan wrote:
That makes sense. Allowing rand would be nice too.
You can now - it's part of :base_math.
Oh, ok. I saw it's not included in :base_core despite being in :base_math,
but didn't realize explicitly including :base_math would bring it back.
What we
One idea would be to use malloc() to allocate storage for the
thread-safe buffers when compiled with thread-safety, rather than using
the stack.
---
Peter Davie wrote:
Hi Tom,
How many of these platforms you use are
Hi,
On Sat, Oct 09, 2004 at 01:31:36PM -0400, Chris Browne wrote:
The most nearly comparable thing is be the notion of partial
indexes, where, supposing you had 60 region codes (e.g. - 50 US
states, 10 Canadian provinces), you might set up indices thus:
[...]
The partial indexes will
On Thu, Oct 14, 2004 at 11:08:54PM +0200, Yann Michel wrote:
BTW: Is there any more documented CVS-version available? I mean it would
be really nice to read some comments from time to time or at least more
comments about each function/method's purpose or functionality.
Huh, the code is
(I apologise for the delayed response.)
At 2004-10-07 01:23:56 -0400, [EMAIL PROTECTED] wrote:
So why is this part of the patch ok? Isn't it going to make libpq get
confused every time a PQExecPrepared sends a v3.0 prepare message?
I thought about that for a while, but I couldn't find
I have modified these reports so they print the full path used.
Typical pg_dumpall output is:
The program pg_dump is needed by pg_dumpall but was not found in the
same directory as /usr/local/postgres/bin/pg_dumpall.
Check your installation.
Hi,
I'm trying to add a -project specific- networking feature to my postgres
build (or database as function). What I want to do is to send a Query
instance (as a String-retrieved through an SPI function) to other
machines and (after they have executed it) to receive result tuples.
It's about a
Katsaros Kwn/nos wrote:
Hi,
I'm trying to add a -project specific- networking feature to my postgres
build (or database as function). What I want to do is to send a Query
instance (as a String-retrieved through an SPI function) to other
machines and (after they have executed it) to receive result
Well, actually no :) ! Thanks for the hint!
But just from curiosity, would the scenario I described work?
I mean is it possible for an SPI process to run in the background while
other SPI calls are made?
Ntinos Katsaros
On Thu, 2004-10-14 at 11:15, Richard Huxton wrote:
Katsaros Kwn/nos
Katsaros Kwn/nos wrote:
Well, actually no :) ! Thanks for the hint!
But just from curiosity, would the scenario I described work?
I mean is it possible for an SPI process to run in the background while
other SPI calls are made?
I don't think so, you're running in a backend process, so you'd need
20 matches
Mail list logo
