to be bumped up
for committer review.
- Josh Williams
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
was still trying to give it sql_help.h.
Quickpatch attached.
Wondered why my attempts to test and review another patch were suddenly
confounded...
regards, tom lane
- Josh Williams
Index: src/tools/msvc/Solution.pm
look at all
like the current one, so no need to waste reviewer cycles on it.
I'll work on a revised version; feel free to mark it as such in the mean
time. Thanks,
- Josh Williams
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
not much more
so than INFORMATION SCHEMA is.) Would that be preferable, over a couple
additional functions?
- Josh Williams
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
, as an immediate practical example the patch modifies psql's
describe-verbose on sequences to show the ownership information...
postgres=# \d+ tbl_id_seq
(...)
Owner: public.tbl.id
- Josh Williams
Index: doc/src/sgml/func.sgml
===
RCS file
,
anything else in this CommitFest in need of a last minute Windows
run-through?
- Josh Williams
* I could envision having the ability to write reviews directly into the
commitfest web app, where one could define and tag sections. Then
anyone curious about a patch's performance implications
On Tue, 2009-07-28 at 23:38 -0400, Josh Williams wrote:
Huh, running the patched version on a single thread with 128 clients
just got it to crash. Actually consistently, three times now. Will try
the same thing on the development box tomorrow morning to get some
better debugging information
some kind of inefficiency either in the PG port or just
something inherent in how the OS works. It does make me wonder where
exactly all that CPU time is going, though. OProfile, how I miss thee.
But that's a different discussion entirely.
- Josh Williams
--
Sent via pgsql-hackers mailing
. Adjusting the worker thread count down to match the number of
cores yielded identical results in the couple of test cases I ran.
Maybe pgbench itself is less of a bottleneck in this environment,
relatively speaking?
- Josh Williams
--
Sent via pgsql-hackers mailing list (pgsql-hackers
. I could see the
correct behavior of these operators being important for GIS
applications. +1 for committer review.
- Josh Williams
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
to get readable information out of pg_depend?
regards, tom lane
- Josh Williams
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
pg_depend wouldn't be seen to change until committed. That, and
ROLLBACK wouldn't work at all...
The column info query is getting messy. Could probably clean that up a
bit if anyone thinks it'd be worth it?
- Josh Williams
Index: src/bin/psql/describe.c
12 matches
Mail list logo