Forwarded Message
Subject: [CORE] Documentation Error: Ceiling, Floor
Date: Tue, 3 May 2016 11:00:10 +0200
From: patrick s.
To: webmas...@postgresql.org, pgsql-c...@postgresql.org
Dear PostgreSQL developers and webmasters
It appears that the documentation of the mathematical
>
Awesome! And a really nice cover.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On 07/28/2015 05:33 PM, Kisung Kim wrote:
> Dear Josh Berkus
>
> Thank you for your reply.
>
> We are translating the PostgreSQL documentation into Korean now
>
> and willing to contribute the results to the community.
That's awesome! I'm looking forward to
about some help translating the
PostgreSQL documentation and error messages into Korean? We could
really use it.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
> suggestion? There is already a previous mention a few sections
> earlier[2] suggesting the use of CONCURRENTLY, so I don't think we
> really need to reiterate that suggestion here.
+1
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mailing list
ew web pages for that which are heavily
referenced, particularly the pgbouncer online docs. I'll try to get new
online docs elsewhere.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On 11/04/2014 01:38 PM, Josh Berkus wrote:
> On 11/04/2014 10:20 AM, Peter Eisentraut wrote:
>> On 10/29/14 6:47 PM, Josh Berkus wrote:
>>> On 10/20/2014 11:04 AM, Peter Eisentraut wrote:
>>>> The 9.4 documentation for streaming replication still starts
On 11/04/2014 10:20 AM, Peter Eisentraut wrote:
> On 10/29/14 6:47 PM, Josh Berkus wrote:
>> On 10/20/2014 11:04 AM, Peter Eisentraut wrote:
>>> The 9.4 documentation for streaming replication still starts out by
>>> making you set up archive_command and restore_comman
tion slots and then go from there?
Well, bluntly, our replication docs should be taken out behind the barn
with an axe. They tell you more about the development history of
PostgreSQL than they tell you about how to replicate.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent
ary_slot_name and such is configured at the
> appropriate place too.
Huh. I can't seem to find any way to navigate to that page. What is it
supposed to be under?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On 09/03/2014 10:43 PM, Josh Berkus wrote:
>
> Section 46.2.2 has this:
>
> Note: PostgreSQL also has streaming replication slots (see Section
> 25.2.5), but they are used somewhat differently there.
>
> Section 25.2.5 has this:
>
> You can avoid this by setting w
early, or by
configuring a replication slot for the standby.
... however, absolutely nowhere is it explained how to configure a
replication slot for a streaming replica. Is it, in fact, possible to
do so?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs
On 08/21/2014 12:20 PM, Bruce Momjian wrote:
> On Thu, Aug 21, 2014 at 11:52:07AM -0700, Josh Berkus wrote:
>> On 08/20/2014 04:12 PM, Bruce Momjian wrote:
>>> On Tue, Aug 19, 2014 at 11:27:47AM -0700, Josh Berkus wrote:
>>>> I'd also like to mention pg_receiv
On 08/20/2014 04:12 PM, Bruce Momjian wrote:
> On Tue, Aug 19, 2014 at 11:27:47AM -0700, Josh Berkus wrote:
>> I'd also like to mention pg_receivexlog, Barman, WAL-E, and RepMgr as
>> external utilites and alternatives.
>
> Yes, please! We need to give users on what
On 08/19/2014 10:39 AM, Tom Lane wrote:
> Josh Berkus writes:
>> Well, if we want a sample command in the docs, then we should actually
>> give a few different sample commands and even a sample shell script. If
>> we give the users several alternatives, maybe they'll
On 08/18/2014 10:31 AM, Tom Lane wrote:
> Josh Berkus writes:
>> 2) One reason users are using the "test -f" version of the archive
>> command is that we put it in the same postgresql.conf. I would suggest
>> that we don't put *any* archive command in the sa
java/sql/DriverManager.html
>
>
>
> Cheers,
>
> Chris
>
>
>
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
nd is that we put it in the same postgresql.conf. I would suggest
that we don't put *any* archive command in the sample postgresql.conf,
since there is no command we can supply which isn't a potential foot-gun.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via
suggestions from people.
Yah? Does it work on Windows?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On 08/11/2014 12:49 PM, Tom Lane wrote:
> Kevin Grittner writes:
>> Josh Berkus wrote:
>>> Yeah, realistically, I think we need to start supplying a script or two
>>> in /contrib and referencing that.� I'm not sure how to make it work for
>>> the Windows
s that
> automatically, like rsync does.
Yeah, realistically, I think we need to start supplying a script or two
in /contrib and referencing that. I'm not sure how to make it work for
the Windows users though.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-d
orage blip, for example), then the
command will fail and will continue to fail forever, ending archiving.
Is there some good reason why "test ! -f" was added to the sample?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgr
Bruce can do that part.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Folks:
http://www.postgresql.org/docs/9.3/static/upgrading.html
... no mention of pg_restore of any kind. Is there any reason why
someone (maybe me) *shouldn't* rewrite this to include pg_restore?
Frankly, I think recommending psql to restore is a bad idea ...
--
Josh Berkus
Postg
On 08/09/2013 07:31 PM, Tom Lane wrote:
> Josh Berkus writes:
>> Actually, on further feedback from the organizer, it's not 2 days, it's
>> *five*. I don't know too many of us who can afford a full week to work
>> on community documentation. Oh well, we
commit. And we've missed the deadline now.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
; dev ecosystem.
Actually, on further feedback from the organizer, it's not 2 days, it's
*five*. I don't know too many of us who can afford a full week to work
on community documentation. Oh well, we'll have to do it on our own :-(
--
Josh Berkus
PostgreSQL Experts Inc.
ht
's up for it?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
> Also the divisions between sections were totally arbitrary and unintuitive.
>
> I think it would make a lot more sense to modify the SGML export to
> create a book per chapter.
Also ... why is this discussion not on pgsql-docs, where it belongs?
Crossing it over.
--
Josh Berku
> I don't know, because I can't see what's changed if you don't send a
> diff. It would be fine if you sent a diff between plain text, to
> illustrate what you mean, even if it's not the actual source code.
Odd; nobody else seems to have had trouble under
> This would be easier to process if you had sent a diff.
Do you agree with the changes? I can send a diff. I personally find
SGML impossible to read, though, so I never propose changes that way.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mail
On 6/15/12 12:25 PM, Jeff Davis wrote:
> On Fri, 2012-06-15 at 11:05 -0700, Josh Berkus wrote:
>> The default, 64, has historically proven sufficient for most databases,
>> but you might need to raise this value if you have clients that touch
>> many different tables in
llows. See Section 17.4.1 for information on how to
adjust those parameters, if necessary.
When running a standby server, you must set this parameter to the
same or higher value than on the master server. Otherwise, queries will
not be allowed in the standby server.
--
Josh Berkus
PostgreSQL E
who
have been using Postgres for years, are unclear on how REVOKEing
privileges on columns is supposed to work.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresq
On 1/12/12 1:43 PM, Euler Taveira de Oliveira wrote:
> On 12-01-2012 17:28, Josh Berkus wrote:
>> Can't open perl script "/bin/collateindex.pl": No such file or directory
>> make[3]: *** [bookindex.sgml] Error 2
>>
> Did you install docbook-dsssl? It must c
're pretty much dependent on openjade
> features that did not exist in plain jade. Maybe we should just get rid
> of our attempts to use the older tool.
Yeah, the problem is that if you install just "openjade" on
debian/ubuntu, it doesn't create the command "jade", w
On 1/12/12 12:28 PM, Josh Berkus wrote:
> To be more specific, having installed all of the requirements listed in
> builddocs, I'm still getting a fatal error:
>
> make[3]: Entering directory `/usr/local/src/test/doc/src/sgml'
> { \
>
gres.sgml
jade:E: unknown warning type "fully-tagged"
LC_ALL=C '/usr/bin/perl' /bin/collateindex.pl -f -g -i 'bookindex' -o
bookindex.sgml HTML.index
Can't open perl script "/bin/collateindex.pl": No such file or directory
make[3]: *** [bookindex.sgml] Err
e named requirements don't
relate at all to debian/ubuntu packages.
We'd probably get more help on the docs if it wasn't a day-long effort
to build them. Sphinx anyone?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs
ted
jade:postgres.sgml:3:0: entity was defined here
... and lots of other errors, eventually fatal.
Requirements for building the docs are not documented in our docs.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org
>>> I'll write up a new version later, just wanted to put this note on the
>>> ML so that somebody would bug me before the end of 9.1 beta.
>>
>> Hey, you!
Well, a bit late now. Clearly posting stuff to the -docs list is not a
good way for me to remember it.
EXTENSION creates that one for you...
Ah, I think I combined code from non-create extension version with the
create extension version. Need to fix that, with both examples.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.
> We could also link to
> <http://pubs.opengroup.org/onlinepubs/007908799/xsh/strftime.html>, for
> example.
That would be helpful. I still think we want a few examples in our
docs, though.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-do
ebody would bug me before the end of 9.1 beta.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make chang
= minute, %a = short
weekday name, and %b = short month name.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs
On 3/2/11 8:35 AM, Robert Haas wrote:
> On Mon, Feb 7, 2011 at 1:47 PM, Josh Berkus wrote:
>> Had to look up some stuff given the splintering of Solaris:
>>
>> ==
>>
>> Solaris 2.6 to 2.9 (Solaris 6 to Solaris 9)
>>
>>The default m
ee "Chapter2:
Projects and Tasks" in the Solaris 10 System Administrator's Guide for
more information on projects and prctl.
===
--
-- Josh Berkus
PostgreSQL Experts Inc.
minimal operating systems the bigint type might not
function correctly, because it relies on compiler support for eight-byte
integers. On such machines, bigint acts the same as integer, but still
takes up eight bytes of storage. (We are not aware of any modern
platform where thi
al integer columns in the same
table with values less than 32,000, you can sometimes achieve
significant space savings by using smallint instead of integer.
Otherwise, using smallint usually results in no real space or memory
savings.
--
-- J
All,
Attached is a patch re-arranging some of the features in the first part
of the release notes, as well as adding a few. The additions are based
on (a) votes on what's a big feature for 9.0, and (b) a desire to match
the features listed elsewhere, such as the press kit.
--
-- Josh B
example script needs to start with:
\set scale 10
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make
Robert,
Updated patch.
P.S. I hate CVS.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
Index: release-9.0.sgml
On 6/24/10 10:30 AM, Robert Haas wrote:
> This part is no longer true:
Right. And I just got an explanation of one of Oleg's patches. Let me
submit a new doc patch if you haven't applied that one yet.
--
-
Bruce,
Still working on it
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
Index: release-9.0.sgml
Bruce,
Still working on the release notes, another interim patch to prevent
conflicts. Are you going after the two patch authors where we need
clarification on their patches?
--
-- Josh Berkus
PostgreSQL Experts Inc
On 5/11/10 3:06 PM, Robert Haas wrote:
> On Tue, May 11, 2010 at 4:41 PM, Josh Berkus wrote:
>> The above assumes that there isn't already a project
>> 101,
>
> I must be missing something, because I don't see the reference to 101.
Editing error. I see an
ator's Guide for
more information on projects and prctl.
(and no, there's no reusable link to the solaris docs)
--
-- Josh Berkus
PostgreSQL Experts Inc.
http
On 5/7/10 5:13 PM, Tom Lane wrote:
> Josh Berkus writes:
>> This is what I have to replace the current fsync entry in config.sgml.
>
> s/unexpected shutdown/system crash/, perhaps. The wording you have
> suggests that a forced Postgres stoppage produces a problem, which it
&g
.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http
Need this sentence added in the Notes section of sql-reassign-owned:
REASSIGN OWNED will not reassign the ownership of any databases owned by
the role. These still need to be changed using ALTER DATABASE.
--
-- Josh Berkus
asible, it wouldn't be hard to
document. That's all.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@po
;s easy to add to the documentation.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to
All,
The libpq-example is using local includes for libpq-fe, instead of
library includes:
#include "libpq-fe.h"
I can't think of a single good reason for this, is there one?
--Josh Berkus
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to yo
m I missing one?
--Josh Berkus
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
"Variable %s Will Not Stay Shared" and "Variable %s is not
available" in the perldiag man page for more details."
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Peter,
I suppose a more constructive point would be, where are the other
constraint types kept track of?
AFAICT, we're not tracking them in pg_class at all anymore, except that
FKs will set relhastrigger=true in the absensce of any other triggers.
The confusion on this particular line is ca
The count was only used to determine if we should check for triggers, so
we now use a boolean; the code checks are the same.
Hmmm. In the beta publicity and release notes, we should warn tool
designers about this. It's quite possible that some of them (SQLManger,
etc.) were using the coun
Bruce,
Currently, catalog-pg-class is a bit confusing as to where FKs are
tracked in pg_class. Please update the lines for relchecks and
reltriggers to read:
relchecks int2 Number of check constraints on the table (but not
other types of constraints); see pg_constraint catalog
Uh, why
int2 Number of triggers on the table, including
constraint-triggers for foreign keys; see pg_trigger catalog
--Josh Berkus
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Folks,
In the Release Notes for 8.3.5, 8.2.11, and 8.1.15, no mention is made
of the need to REINDEX GiST indexes for some users. Please add this
sentence to each Migration to Version section.
Please update soon; people are being confused between the apparent
contradiction between the Releas
that mischaracterization is worth bothering the
> translators over.
Sounds like I'd better. Sending out this afternoon.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
All,
Just FYI, it's going to be difficult to replace the name of the feature in
the PR docs at this point; I already have 11 translations. What's *wrong*
with "Load Distributed Checkpoint", which is what we've been calling it
for 6 months?
--
--Josh
Josh Be
Tom,
If we do want to keep credits in the SGML pages, how extensive should
they be? I already took it on myself to remove Gene Selkov's snailmail
address, but do we even want email addresses there? A lot of them are
probably dead, and the ones that aren't are causing their owners to get
extra
on may not
be handling data type comparisons cleanly, you are strongly urged to test
for casting error messages before upgrading your production server.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 7: You can
kaging, I'm thinking the "restore casts"
package is essential rather than being a nice idea.
Should I be discussing this on a different list?
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 9: In vers
ng will break a lot more users).
2) They need to check for bugs
3) If Robert gets his type-cast backport package together, the location of
that.
I'm thinking this warning should go (prominently) into the release notes,
the community notice, and the extended web release.
--
--Josh
Josh Ber
the Shoelaces example and the final paragraph about RETURNING,
finishing with:
"...the RETURNING clause is simply ignored for INSERT."
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
tion from you on, rather than having you distracted
> cleaning up documentation that's perfectly functional for now.
What kind of data? On bgwriter_lru autotuning?
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
or "Appendices". Also, I don't think it's necessary to make each
command option a separate subchapter, but I can see how that would be hard to
avoid in an automated system.
Guys, would it be out of the question to do this in 8.3? Please please?
If we go ahead with this,
lient).
Do we have a doc todo list somewhere?
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Bruce,
http://www.postgresql.org/docs/8.2/interactive/release-7-4-15.html
... no mention of the CAN/AU DST update. There's also no mention in
8.2.1, but I'm assuming that's because 8.2.0 was DST-correct?
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
s available via Emacs-SGML, but there are a lot more tools
which do it for XML (including Emacs).
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
ction of the document
> you are in.
Sure, but that doesn't do any good if you want to cut-and-paste a section
and fix the tags.
Anyway, from the sound of it whether or not there are better authoring
tools for XML than SGML is "undetermined pending further investigation."
--
--Josh
CVS in the meantime. I gave
up.
If the docs were WYSWYG-editable or if we had any authoring tool which
would automatically fix tags, I would have been able to make the changes
and submit a patch in < 4 hours, not 15 hours+ it would have taken to
complete the project.
--
--Josh
Josh
than hand-editing text files. No such tool exists for SGML --
even the Emacs toolkit merely does validation.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
sites
> when they need one.
Aha, got it. OK, so this just needs a good example ... will try to think of
one.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 6: explain analyze is your friend
Tom,
> Uh, why do you think that's significant? The stype is whatever you
> need to use.
Right, but do you have two stypes for a multi-col, a single stype, or a
composite stype? The docs don't say and it's not obvious.
--
Josh Berkus
PostgreSQ
many authoring tools which
support only XML as support SGML -- and that most of the tools which
support SGML are out-of-maintenance.
--Josh Berkus
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Folks,
So I don't forget this:
The docs do not have an example of creating a multi-column aggregate,
and the syntax is NOT obvious. For example, what do you use for stype
in a multi-col aggregate?
--Josh
---(end of broadcast)---
TIP 6: explai
ry node in the cluster.
> You still have to be very careful with how you use it, but not nearly
> as much as with simpler solutions.
I think the general term is "statement-based replication", not "broadcasting".
--
Josh Berkus
PostgreSQL @ Sun
San Francis
Bruce,
> Most people didn't want a list because there is no way to keep it
> current in the docs, and a secondary web site was suggested for the
> list.
So, like www.postgresql.org/docs/techdocs/replication? That would work.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
27;ve seen no discussion of the matter. I think we should have
them.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index sc
Bruce,
> > > ftp://momjian.us/pub/postgresql/mypatches/replication
I'm still not seeing anything in this patch that tells users where they can
get replication solutions for PostgreSQL, either OSS or commercial.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
i/cluster, and Mammoth Replicator.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
ch are available for PostgreSQL and how to get
them.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECT
than anything else.
BTW, is the Dtrace build docs straightened out, or do I still need to patch
it? i.e. does it acurrately reflect that you need Solaris 10 update3 or
OpenSolaris to build, currently?
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---
;m not sure how much I should be writing up for the main docs and how much
keeping on the DTrace project page. Help?
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 6: explain analyze is your friend
JD,
> Josh... then why didn't you just submit a patch?
See earlier conversation about the lack of good tools for Docbook/SGML.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 4: Have you searched
n do this via the command "su - postgres"; otherwise simply log into
the system as that system user. Once you are logged in as the
installation owner, you can use createuser to add other accounts."
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---
attract new Doc contributors (like *me*) by
allowing them to use tools which to not require them to spend more time
tagging their text than writing it.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)---
TIP 3: Have y
1 - 100 of 166 matches
Mail list logo
