Andrew Kroeger <[EMAIL PROTECTED]> writes:
> With the table definitions you posted, one of the first things I noticed
> was that the default value for an integer column was a bigint value. I
> did some quick 32-bit math and found that the smallest legal 32-bit
> integer value is -2147483648, not -
On Thu, Aug 02, 2007 at 09:14:37AM -0700, Alan Hodgson wrote:
> On Thursday 02 August 2007 09:02, "Bryan Murphy" <[EMAIL PROTECTED]>
> wrote:
> > My question: Is there a way I can decrease the priority of a specific
> > query, or determine the PID of the process it is running in? I'd like
> > to
Sven Clement wrote:
> Table: "public.tmdata"
...
> id| integer | default -2147483684::bigint
...
> Table: "public.tmdataintervalsec"
...
> id| integer | default -2147483684::bigint
Not that this directly addresses the performance issues you described,
but
On Fri, 2007-08-03 at 16:09 -0400, Jignesh K. Shah wrote:
> This patch seems to work well (both with 32 and 64 value but not with 16
> and the default 8).
Could you test at 24 please also? Tom has pointed out the additional
cost of setting this higher, even in workloads that don't benefit from
Hi Simon,
This patch seems to work well (both with 32 and 64 value but not with 16
and the default 8). Is there a way we can integrate this in 8.3?
This will improve out of box performance quite a bit for high number of
users (atleat 30% in my OLTP test)
Regards,
Jignesh
Simon Riggs wrote
On Fri, 2007-08-03 at 13:58 -0400, Mouhamadou Dia wrote:
> Hello,
>
> I have a Postgres instance (version 8.1) running on a Solaris 10
> machine. When I run the following query
>
>
>
> SELECT * FROM PROR_ORG, ( ( ( ( (PRPT_PRT LEFT OUTER JOIN
> PRPT_PRTADR ON
>
> PRPT_PRT.PRT_NRI = PRPT_PR
Hello,
I have a Postgres instance (version 8.1) running on a Solaris 10
machine. When I run the following query
SELECT * FROM PROR_ORG, ( ( ( ( (PRPT_PRT LEFT OUTER JOIN PRPT_PRTADR
ON
PRPT_PRT.PRT_NRI = PRPT_PRTADR.PRT_NRI AND PRPT_PRTADR.ADR_F_DEF=true)
LEFT OUTER JOIN PLGE_CTY ON PRP
Sven,
> The hardware is a IBM X306m Server, 3.2 GHz HT (Pentium IV), 1 GB RAM
> and 2x 250 GB HDD (SATA-II) with ext3 fs, one of the HDD is dedicated to
> database. OS is Debian 3.1 Sarge with PostgreSQL 7.4.7 (7.4.7-6sarge1)
> with the libpq frontend library.
Note that 7.4.7 is not the current b
Hi,
First thank you already for your answers, as we are working in an
environment with NDA's I have first to check all the queries before I may
publish them here, but the structure of the DB is publishable:
2 Tables:
Table: "public.tmdata"
Column|Type |Modifiers
--
On 3 Aug 2007 at 6:52, Sven Clement wrote:
> Hello everybody,
>
> as I'm new to this list I hope that it is the right place to post this
> and also the right format, so if I'm committing an error, I apologize
> in advance.
>
> First the background of my request:
>
> I'm currently employed by an
On Fri, 2007-08-03 at 06:52 -0700, Sven Clement wrote:
> Hello everybody,
>
> as I'm new to this list I hope that it is the right place to post this
> and also the right format, so if I'm committing an error, I apologize
> in advance.
>
> First the background of my request:
>
> I'm currently em
Hello everybody,
as I'm new to this list I hope that it is the right place to post this and
also the right format, so if I'm committing an error, I apologize in
advance.
First the background of my request:
I'm currently employed by an enterprise which has approx. 250 systems
distributed worldwid
12 matches
Mail list logo
