On Thu, 2004-01-01 at 03:22, Oliver Elphick wrote:
> What is needed to provide spinlock support for linux on hppa?
I should add that 7.3.4 built OK.
--
Oliver Elphick[EMAIL PROTECTED]
Isle of Wight, UK http://www.lfix.co.uk/oliver
GPG:
What is needed to provide spinlock support for linux on hppa?
make[5]: Entering directory
`/build/buildd/postgresql-7.4.1/build-tree/postgresql-7.4.1/src/backend/access/transam'
...
hppa-linux-gcc -O2 -fno-strict-aliasing -g -Wall -Wmissing-prototypes
-Wmissing-declarations -pipe -I../../../../s
Barry,
Ok, so if we drop this limitation then we leave it up to the architect
to manage the caching problem themselves.
The class loader issue is interesting, this would mean that each object
static or otherwise would not be able to overwrite others data.
--dc--
On Wed, 2003-12-31 at 19:34, Barr
Jan,
In Oracle a call from sql into java (be it trigger, stored procedure or
function), is required to be a call to a static method. Thus in Oracle
all the work is left for the programmer to manage object instances and
operate on the correct ones. While I don't like this limitation in
Oracle
Jan Wieck wrote:
> As an example, if a PL/Java trigger on the order header executes an SPI
> query on the order lines, a trigger on the order line (also in PL/Java)
> might now want to call a method on it's parent object (the order header
> that is waiting for the SPI result set). This should NO
[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:
> http://khack.
I have included the JDBC mailing list since I guess most Java developers
are around here, but not necessarily on Hackers.
Dave Cramer and I where discussing a few issues about the PL/Java
implementation last night and would like to get more input and
suggestions on the matter.
The basic questi
ivan wrote:
but , all in all, do you think that now it is ok ?
No, I don't. I just prefer complete solutions over patchwork.
Jan
On Wed, 31 Dec 2003, Jan Wieck wrote:
ivan wrote:
> why all backend can not using one cache, which would be always
Variable sized shared memory with garbage collection
On Wed, 31 Dec 2003, Tom Lane wrote:
> > Is ABS enough on a 64-bit architecture ?
>
> That was pseudocode, I wasn't actually planning to rely on a function.
> Something more like
>
> longdiff;
FWIW, ISO has a ptrdiff_t, which may be useful here.
Matthew.
> diff = stack_base_ptr
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:
http://khack.osdl.org/stp/285062/
PostgreSQL 7.4.1
--On Wednesday, December 31, 2003 11:20:49 -0500 Tom Lane
<[EMAIL PROTECTED]> wrote:
Gaetano Mendola <[EMAIL PROTECTED]> writes:
Is ABS enough on a 64-bit architecture ?
That was pseudocode, I wasn't actually planning to rely on a function.
Something more like
long diff;
diff = stack_
but , all in all, do you think that now it is ok ?
On Wed, 31 Dec 2003, Jan Wieck wrote:
> ivan wrote:
> > why all backend can not using one cache, which would be always
>
> Variable sized shared memory with garbage collection for SPI plans?
>
> > in real state ... or i can just clear only my c
Gaetano Mendola <[EMAIL PROTECTED]> writes:
> Is ABS enough on a 64-bit architecture ?
That was pseudocode, I wasn't actually planning to rely on a function.
Something more like
longdiff;
diff = stack_base_ptr - &stack_top_loc;
if (diff < 0)
diff = -di
ivan wrote:
why all backend can not using one cache, which would be always
Variable sized shared memory with garbage collection for SPI plans?
in real state ... or i can just clear only my cache, at first
(if i know that this relation could has another oid)
and then normal using relations ?
As sai
i didnt find gethostbyaddr, could be this in default implementation ?
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
why all backend can not using one cache, which would be always
in real state ... or i can just clear only my cache, at first
(if i know that this relation could has another oid)
and then normal using relations ?
or ... just turn off cache, because its strange to has possible
using drop, create et
Tom Lane wrote:
Comments?
Really ugly but effective.
Is ABS enough on a 64-bit architecture ?
Or is better use labs ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscrib
ivan wrote:
as new know plpgsql has special cache which remember too long (event
non-existing tables (i mean old oid)) so i suggest to create same function
only in plpgsql which would clear this cache, or sth like this ?
for ie, where i drop table i would do plpgsql_clear_cache ();
and when i will
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: 31 December 2003 02:41
> To: PostgreSQL-development
> Cc: Tom Lane; Peter Eisentraut; [EMAIL PROTECTED]
> Subject: Re: [HACKERS] [PATCHES] Quoting of psql \d output
>
> We have been discussing this patch on th
19 matches
Mail list logo
