Bruce,
Patch applied. Thanks.
Great. 'cause I need to patch the patch, due to a cut-and-paste error. Next
patch coming Friday, much less extensive than this one.
Is the HAS_RENDEZVOUS GUC still coming? Is there docs for it?
--
Josh Berkus
Aglio Database Solutions
San Francisco
. Is SHOW_BTREE gone, or is it just a Source Developer Option?
--
-Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 8: explain analyze is your friend
just been
re-named to LOG_BTREE_BUILD_STATS. Is this a mistake in GUC.c, or should
I put it back in Runtime.SGML under the new name?
--
-Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 8: explain analyze
.
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
that READ ONLY transactions were *not* a security
feature and that trying to make them one would work very poorly.
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
same defaults with
this patch as without, so no changes to initdb should be required.
--
-Josh Berkus
__AGLIO DATABASE SOLUTIONS___
Josh Berkus
Enterprise vertical business[EMAIL PROTECTED]
and data analysis
bug, intended to make
postgresql.conf easier to understand, so even if some beta tester doesn't
load it, postgresql.conf still works ..
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
Bruce,
Re-building CVS I noticed that I never submitted this doc-only patch to
postgresql.conf.sample.
--
Josh Berkus
Aglio Database Solutions
San Francisco
Index: postgresql.conf.sample
===
RCS file: /projects/cvsroot/pgsql
-compatibility.
Oh, and Bruce, I can't imagine needing specific relkind so I think that
part's fine.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Tom, all,
SELECT: currval
UPDATE: nextval, setval
USAGE: nextval, currval
+1.
--Josh
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
objects, we should do it for all objects. Otherwise we
risk a considerable amount of user confusion.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Zdenek, Bruce,
Has anyone updated the Solaris portion of runtime.sgml yet?
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Neil,
Sure, I'll wait for 8.3 to branch.
I have some cleanup I want to do for 8.3 too.
Josh Berkus
PostgreSQL @ Sun
San Francisco 415-752-2500
---(end of broadcast)---
TIP 6: explain analyze is your friend
applications,
compression is a bad tradeoff.
If, however, CPU used for compression is made up elsewhere through smaller
file processing, then I'd agree that we don't need a switch.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast
than command-line compression for log-shipping? e.g.
why do we need it in the database?
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
wal_fullpage_optimization quite baffling
and I think our general user base will find it even more so. Now that I have
Koichi's explanation of the problem, I vote for simply slaving this to the
PITR settings and not having a separate option at all.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
amount of log we put out for an OLTP server,
for example.
Not that pg_compresslog isn't useful on its own for improving warm standby
managability, but it's completely separate from addressing the we're logging
too much issue.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
PGACE to see
if this implementation is (still) generic enough to support TS as well. If
it is, then it's probably generic enough to be a general building block.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes
Tom,
I think this patch is plenty complicated enough without adding useless
restrictive options.
+1 for no additonal GUC options.
--Josh Berkus
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
that TRUST is inherently insecure, and that's what people are going
to use if they can't get IDENT to work.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
Florian,
I'd be *very* interested in how they come to that assessment. I'd have
thought that the only alternative to getpeereid/getupeercred is
password-based or certificate-based authenticated - which seem *less*
secure because a) they also rely on the client having the correct uid
or gid (to
.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
22 matches
Mail list logo
