Jan Wieck wrote:
The basic question is the definition of the lifetime of an object and
it's identificaition when doing nested calls in this context. In the
OO world, ideally a real world object is translated into one instance
of a class. And complex structures are trees of instances, possibly
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> ... copy the slock_t definition for hppa from hpux.h into linux.h ...
>
> > I think he also has to modify src/include/port/linux.h to support the HP
> > processor.
>
> That's what I said, I thought.
Oh, I saw sl
On Dec 26, 2003, at 4:04 PM, Tom Lane wrote:
Eric Ridge <[EMAIL PROTECTED]> writes:
Xapian has it's own storage subsystem, and that's what I'm using to
store the index... not using anything internal to postgres (although
this could change).
I would say you have absolutely zero chance of making it w
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> ... copy the slock_t definition for hppa from hpux.h into linux.h ...
> I think he also has to modify src/include/port/linux.h to support the HP
> processor.
That's what I said, I thought.
regards, tom lane
-
Jan Wieck <[EMAIL PROTECTED]> writes:
> But can you tell me how to actually check if a saved SPI plan
> references that particular catalog object or not?
This is certainly doable in principle. recordDependencyOnExpr()
contains much of the logic that would be needed -- it would need to be
modified
Tom Lane wrote:
> I think it might be possible to develop a localized patch for 7.4 that
> only affects linux-hppa and doesn't risk breaking anything else: copy
> the slock_t definition for hppa from hpux.h into linux.h and add the
> inline'd version of hppa tas() from CVS tip into s_lock.h. But I
ivan wrote:
may be postgres can use same way like triggers working,
and when relation is droping ( what is equal to delete from pg_class)
there could be something like trigger after .. which can
waiting for CREATE or DROP command, and then clean-up cache,
(for each backend).
This could be for exam
Bruce Momjian wrote:
[EMAIL PROTECTED] wrote:
Hi Manfred,
Just wanted to let you know I tried your patch-spinlock-i386 patch on
our STP (our automated test platform) 8-way systems and saw a 5.5%
improvement with Pentium III Xeons. If you want to see those results:
PostgreSQL 7.4.1:
htt
Oliver Elphick <[EMAIL PROTECTED]> writes:
> I saw the changes to s_lock.h, but I couldn't at first sight see how to
> alter 7.4.1 to incorporate them, because they coincided with a file
> reorganisation.
That's right. The change depends on Bruce's reorganization of the
spinlock configuration mec
On Thu, 2004-01-01 at 17:58, Tom Lane wrote:
> Oliver Elphick <[EMAIL PROTECTED]> writes:
> > On Thu, 2004-01-01 at 03:22, Oliver Elphick wrote:
> >> What is needed to provide spinlock support for linux on hppa?
>
> Possibly nothing --- can you try CVS tip? Bruce has already committed
> his patch
Oliver Elphick <[EMAIL PROTECTED]> writes:
> On Thu, 2004-01-01 at 03:22, Oliver Elphick wrote:
>> What is needed to provide spinlock support for linux on hppa?
Possibly nothing --- can you try CVS tip? Bruce has already committed
his patch to decouple CPU and OS assumptions there, and I changed
Barry,
This appears in principal to be very close to a servlet container. I'm
wondering if we could just use something like jetty as the basis for the
work?
It has already defined class loading per the servlet spec. It is already
setup to handle multiple requests, and load balancing, etc.
Dave
may be postgres can use same way like triggers working,
and when relation is droping ( what is equal to delete from pg_class)
there could be something like trigger after .. which can
waiting for CREATE or DROP command, and then clean-up cache,
(for each backend).
This could be for example same mes
how can i change default time format because now i have for example
2004-01-01 16:51:46.995927 but i want only 2004-01-01 16:51:46, with out
millisec. a tryed with Data-Style but there arent custom style :/
---(end of broadcast)---
TIP 6: Have yo
14 matches
Mail list logo
