On 7/31/07, Andreas Tille <[EMAIL PROTECTED]> wrote:
http://www.physiol.ox.ac.uk/Computing/Online_Documentation/postgresql/plpgsql.html#PLPGSQL-OVERVIEW
>
> Note: The PL/pgSQL EXECUTE statement is not related to the EXECUTE
> statement supported by the PostgreSQL server. The serv
Hi Luke,
On the same page of Solaris internals wiki you may find links to the
study with db_STRESS benchmark (done on UFS and ZFS with PostgreSQL,
MySQL and Oracle (well, Oracle results are removed, but at least I may
say it entered into the same tuning as PgSQL). Tests were done on
Sol10u3 (as we
Yep quite a bit of transactions .. But the piece that's slow is where it
is clearing it up in CommitTransaction().
I am not sure of how ProcArrayLock is designed to work and hence not
clear what we are seeing is what we expect.
Do we have some design doc on ProcArrayLock to understand its purp
Simon,
> Well thats pretty weird. That code path clearly only happens once per
> transaction and ought to be fast. The other code paths that take
> ProcArrayLock like TransactionIdIsInProgress() and GetSnapshotData()
> ought to spend more time holding the lock. Presumably you are running
> with a
Camilo Porto wrote:
>
> Hello,
>
> I would like to better understand the semantics of the statistics shown in
> PostgreSQL Logs. For example, in the report:
>
> DETAIL: ! system usage stats:
> ! 0.000100 elapsed 0.00 user 0.00 system sec
> ! [0.016997 user 0
8.2.3
Thanks
Regards
Sachchida N Ojha
[EMAIL PROTECTED]
Secure Elements Incorporated
198 Van Buren Street, Suite 110
Herndon Virginia 20170-5338 USA
http://www.secure-elements.com/
800-709-5011 Main
703-709-2168 Direct
703-709-2180 Fax
This email message and any attachment to this email message is
On 7/31/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Merlin Moncure" <[EMAIL PROTECTED]> writes:
> > third (but unlikely) possibility is there are various dropped tables,
> > etc which need to be deleted but there are stale postgresql processes
> > holding on to the fd. This would only happen follow
Sachchida Ojha wrote:
>
> Hello,
> I am getting following error from my application. Can any body tell me
> how to find the process name and transaction details when the deadlock
> occurred?
>
> This problem did not occur consistently.
>
> Error log
>
> 2007-07-30 19:09:12,140 ERROR [se.em.as
Hello,
I am getting following error from my application. Can any body tell me
how to find the process name and transaction details when the deadlock
occurred?
This problem did not occur consistently.
Error log
2007-07-30 19:09:12,140 ERROR [se.em.asset.persistence.AssetUpdate]
SQLException ca
Hello,
I would like to better understand the semantics of the statistics shown in
PostgreSQL Logs. For example, in the report:
DETAIL: ! system usage stats:
! 0.000100 elapsed 0.00 user 0.00 system sec
! [0.016997 user 0.006998 sys total]
! 0/0
Hi,
I have found under
http://www.physiol.ox.ac.uk/Computing/Online_Documentation/postgresql/plpgsql.html#PLPGSQL-OVERVIEW
Note: The PL/pgSQL EXECUTE statement is not related to the EXECUTE
statement supported by the PostgreSQL server. The server's EXECUTE
stateme
Hello list,
I have a problem with a simple count query on a pgsql 8.2.3 server.
SELECT COUNT(pk_file_structure_id) FROM tbl_file_structure INNER JOIN
tbl_file ON fk_file_id = pk_file_id WHERE lower(file_name) like lower
('awstats%');
Using Explain analyze I've noticed that it makes a seq scan
12 matches
Mail list logo
