[EMAIL PROTECTED] (Robert E. Bruccoleri) writes:
> With two processors running the same query, it appears to be a
> slowdown. When I look at the system calls, the backends were
> executing about one read per second. With six processors running the
> same query, it appeared to be a deadlock -- no
[EMAIL PROTECTED] writes:
> CREATE FUNCTION exceptions(int4) RETURNS setof varchar(64) AS '
> SELECT property_id
> FROMitm_exception
> WHERE item_id = $1
> ' LANGUAGE 'sql';
> CREATE VIEW itm_property_ALL AS
> SELECT *
> FROMitm_property
>
Arcady Genkin <[EMAIL PROTECTED]> writes:
> Can I redefine location of the UNIX domain socket file to be other
> than /tmp/.s.PGSQL.5432?
Yes, in 7.1 this is a supported option. See unix_socket_directory
parameter.
regards, tom lane
---(end of br
Dear Tom,
>
>
> [EMAIL PROTECTED] writes:
> > Apparent deadlock for simultaneous sequential scans
>
> > However, if more than one application is run at once, the performance
> > deteriotates drastically.
>
> So is it a deadlock, or a slowdown? How many is "more than one"?
With two processors
I've been using postgresql for a quite some time and I have nothing to say
about it except it is wonderfull.
I recently upgraded to linux redhat 7.1 that had postgresql 7.0.3 on it and
started using it.
I know I should upgrade to the latest version but since I was behind on time
and I'm not
