Am Freitag, 22. Februar 2013, 14:35:25 schrieb Heikki Linnakangas:
> On 22.02.2013 10:25, Markus Schulz wrote:
> > i can run the query four times with good performance and after that
> > postgresql starts with the strange lseek() behavior.
>
> By default, the JDBC driver
hello,
i have a strange and reproducible bug with some select queries and 64bit
postgresql builds (works fine on 32bit builds).
The postgres process will run with 100% cpu-load (no io-wait) and strace
will show endless lseek(..., SEEK_END) calls on one table for minutes.
lseek(28, 0, SEEK_END)
Am Samstag 04 Dezember 2010 schrieb Tom Lane:
> "Kevin Grittner" writes:
...
> > One option would be to create a different user for running queries
> > which read from complex views such as this.
>
> If you don't want to change the collapse limits, the only other
> option is to restructure this s
Am Samstag 04 Dezember 2010 schrieb Kevin Grittner:
> One option would be to create a different user for running queries
> which read from complex views such as this.
>
> postgres=# create user bob;
> CREATE ROLE
> postgres=# alter user bob set from_collapse_limit = 40;
> ALTER ROLE
> postgres=# a
Am Freitag, 3. Dezember 2010 schrieb Kevin Grittner:
> Markus Schulz wrote:
> > i have a big performance problem
> >
> > [joining two complex views for reporting]
>
> What version of PostgreSQL is this? How is PostgreSQL configured?
> (The postgresql.conf file wit
hello,
i have a big performance problem with some views which would joined
(from the third party tool crystal reports) to print a document.
view1:
SELECT ...
FROM
personen.kunde kunde,
personen.natuerliche_person person,
viewakteur akteur,
personen.anschrift adresse,
personen.kon
