Peter Eisentraut wrote:
> On 8/22/17 09:36, sahapa...@gmail.com wrote:
> > Hi all,
> > There isn't any link between 9.4 - replication slot page and other newer
> > ones.
> >
> > check pages;
> >
> > https://www.postgresql.org/docs/9.4/static/catalog-pg-replication-slots.html
> > https://www.po
Tom Lane wrote:
> How do we get rid of those duplicative (and not-appropriate-to-the-
> main-topic) links on the first line?
Hmm, is it related to this previous report of mine?
https://postgr.es/m/20170315160525.42x4wxtdhk3sa522@alvherre.pgsql
--
Álvaro Herrerahttps://www.2ndQua
jonny.batti...@gmail.com wrote:
> In this section:
> https://www.postgresql.org/docs/10/static/logical-replication-config.html
>
> the following sentences make no sense in the way replication slots are
> designed:
>
> "The subscriber also requires the max_replication_slots to be set. In
> this
None wrote:
> Hi all,
>
> Thank you. I'm using 9.6. I found all the available options in the
> 'postgresql.conf' file on the server itself. The explanations are good, but
> I was looking for something like this:
>
> # minimal, archive, hot_standby, or logical
>
> I saw the 'replica' option in th
Daniel Gustafsson wrote:
> With 8.1 being fairly far down on the EOL list, it seems about time to update
> the docs regarding PG_MODULE_MAGIC to mention the pre-8.2 #ifdef guards as an
> exception and not the default. Not sure if a Note should be used, or just a
> paragraph, so opted for a paragra
Michael Paquier wrote:
> (Spotted a transation issue, so added Álvaro in the loop)
> Álvaro, I think that those translations are incorrect:
> src/backend/po/fr.po:#~ msgid "Make sure the root.crt file is present
> and readable."
> src/backend/po/ja.po:#~ msgid "Make sure the root.crt file is prese
Simon Riggs wrote:
> On 31 July 2017 at 22:13, wrote:
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/9.6/static/release-9-6.html
> > Description:
> >
> > Wondering why PostgreSQL still uses the terms master and slave when ther
Alvaro Herrera wrote:
> d...@dbi-services.com wrote:
> > The following documentation comment has been logged on the website:
> >
> > Page:
> > https://www.postgresql.org/docs/10/static/functions-event-triggers.html
> > Description:
> >
> > The tab
Alvaro Herrera wrote:
> case.roll...@gmail.com wrote:
>
> > "Possibly, your site administrator has already created a database for
> > your
> > use. He should have told you what the name of your database is."
> >
> > should be
> >
> >
d...@dbi-services.com wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/static/functions-event-triggers.html
> Description:
>
> The tables under 9.28.1. and 9.28.2. don't look like they should, I
> believe
Odd. I wonder wha
case.roll...@gmail.com wrote:
> "Possibly, your site administrator has already created a database for
> your
> use. He should have told you what the name of your database is."
>
> should be
>
> "Possibly, your site administrator has already created a database for
> your
> use. They should hav
tgooda...@gmail.com wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.1/static/runtime-config-query.html
> Description:
>
> "Better ways to improve the quality of the plans chosen by the optimizer
> include adjusting the plane
Magnus Hagander wrote:
> > The easiest way to fix the one that Daniel reported would be to just make
> > it have the same name as before, wouldn't it? That would also automatically
> > fix any other cases that would possibly link to LEGALNOTICE. (AFAIK this is
> > the only file that was caps befor
Daniel Gustafsson wrote:
> The Legal Notice page has in 10 changed from being uppercased to lowercased,
> and in the process the site no longer sees it as being present in previous
> version of the documentation:
>
> https://www.postgresql.org/docs/9.6/static/LEGALNOTICE.html
> https://www.postgre
While reviewing Tomas' extended statistics patch I noticed that the new
docbook toolchain produces additional links for each indexterm, based on
the tags there are. For instance, in 9.5 I see this:
statistics, Aggregate Functions, The Statistics Collector
of the planner, Statistics Used by t
Peter Eisentraut wrote:
> The questions for those who are building PDFs are
>
> - Can you make the build work?
It worked fine for me after installing the "fop" package. No need to
rerun configure.
> - Does the output look OK?
It looks generally sane in a very quick skim, modulo the problems w
hvrau...@gmail.com wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.5/static/sql-copy.html
> Description:
>
> The documentation describes:
> [ [ WITH ] ( option [, ...] ) ]
>
> But actually the options are only separated b
Alexander Law wrote:
> 14.09.2016 18:30, Alvaro Herrera wrote:
> >What's up with 30?
>
> ecpg.sgml contains "The scope of the allocated descriptor is
> WHAT?.", which is printed with XSLT but ignored with DSSSL.
>
> Maybe we can just remove such remarks
Jürgen Purtz wrote:
> Hello Alexander,
>
> great job!
>
> In my opinion most of the differences are not only acceptable but even
> better.
Agreed. But there are a few that merit a fix. There are a few that look
a matter of style (XSL output looks odd), another few are not important.
But I thin
Barbara Sims wrote:
> Hi,
>
> Just wanted to let you know about a link that seems to be broken on this page
> http://tpchihuahua.uach.mx/cvsup.html.
>
> It is this link http://www.research.digital.com/SRC/modula-3/html/home.html,
> but the site doesn’t seem to be active any more. I thought you
David G. Johnston wrote:
> If we are looking to improve things here I'd at least consider having the
> default cascade to be safe and not drop persisted data (I suppose that
> could functions linked to functional indexes...) and have a separate flag
> that would also be permitted to destroy data.
Tom Lane wrote:
> > also, object locks need to be acquired, which
> > can be very troublesome if you discover that some frequently-used object
> > is in the set to be dropped, by some unfortunate accident.
>
> You'd need the object locks in any case, to be sure things hold still long
> enough for
Tom Lane wrote:
> Alvaro Herrera writes:
> > I think it'd be a good idea to add some more discoverability: what would
> > be deleted if an object X were to be deleted?
>
> There's plenty of discoverability already. The documentation suggests
>
>(If yo
Tom Lane wrote:
> I'm inclined to suggest that maybe the generic phrasing could be
> "Automatically drop objects that depend on the [(such as ...)],
> and in turn all objects that depend on those objects".
I think it'd be a good idea to add some more discoverability: what would
be deleted if an
Peter Eisentraut wrote:
> The NOTIFY man page writes
>
>When NOTIFY is used to signal the occurrence of
> changes
>to a particular table, a useful programming technique is to put the
>NOTIFY in a rule that is triggered by table updates.
>
> Is using rules here still best practice? Th
Kevin Grittner wrote:
> On the other hand, try connecting to a database with
> psql and typing:
>
> \h create index
>
> ... (or any other command name). The help you get there is fished
> out of the docs.
BTW I noticed a few days ago that we don't have a "where BLAH can be one
of" section for
Peter Geoghegan wrote:
> The best argument for ICU is the evidently lax attitude that the glibc
> people have towards the correctness and consistency of their
> collations:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1320356#c3
>
> Here, Carlos O'Donnell, a glic committer, says "Regarding (b
Tom Lane wrote:
> Alvaro Herrera writes:
> > Right; mschwan wrote private email to indicate that the function in
> > question is:
>
> > CREATE OR REPLACE FUNCTION public.f_unaccent(text)
> > RETURNS text AS
> > $$
> > select public.unaccent('
Alvaro Herrera wrote:
> Michael Paquier wrote:
> > On Tue, Jun 21, 2016 at 1:00 AM, wrote:
> > > Page: https://www.postgresql.org/docs/9.5/static/sql-dropextension.html
> > > Description:
> > > I dropped an extension in my database with a function depende
our own function depends on,
but your own function remains in place.
This seems very similar to the use case for which we added the ALTER
OBJECT DEPEND ON EXTENSION (cited below) but not quite the same.
Perhaps mschwan can clarify.
commit f2fcad27d59c8e5c48f8fa0a96c8355e40f24273
Author: Alvaro H
Bruce Momjian wrote:
> On Fri, Jun 17, 2016 at 06:01:59PM -0400, Bruce Momjian wrote:
> > On Fri, Jun 17, 2016 at 05:51:54PM -0400, Alvaro Herrera wrote:
> > > Bruce Momjian wrote:
> > > > The attached patch documents that pg_upgrade requires old/new servers to
>
Bruce Momjian wrote:
> The attached patch documents that pg_upgrade requires old/new servers to
> use compatibile collation library versions as well.
I think this is way too thin to be helpful:
> --- 61,68
> checking for compatible compile-time settings, including 32/64-bit
> binarie
Tom Lane wrote:
> =?UTF-8?Q?J=c3=bcrgen_Purtz?= writes:
> > a) In my opinion this wording is easier to understand because it avoids
> > the negation via "not less".
>
> That's a fair point.
>
> The other difference is least/greatest versus smallest/largest. I'm not
> sure if using least/great
星合 拓馬 wrote:
> Hi all,
>
> In the Release Notes 9.5, it seems that one parameter name is incorrect.
> In the Monitoring of Changes section,
> parameter called log_min_autovacuum_duration is incorrect.
> log_autovacuum_min_duration is correct.
It seems I typo'ed the parameter name in the commit me
Jürgen Purtz wrote:
> after some manual interventions (which must become part of an algorithm)
> it's possible to created the complete PDF file for the db4 production chain:
> *.sgml -- (perl) --> *.xml and after that step: postgres.xml -- (evaluate
> XInclude with xmllint) --> postgres_all.xml --
Jürgen Purtz wrote:
> Hello Alvaro,
>
> yes, character entities respectively their values must be kept (what you
> have seen is an intermediate state). We will use utf-8, so every possible
> Unicode code point can be used directly. But we use not only character
> entities, there are also parameter
Jürgen Purtz wrote:
> The real challenge is the second
> step as it implies some manual modifications (entities, non-valid markup in
> sense of db5-schema) and a switch to a different output chain. Maybe we can
> live for a while with some files, which are not valid against db5-schema -
> as far a
Alexander Law wrote:
> Hello Jürgen,
>
> As was stated in the aforementioned thread, solution 2 can be much (8x)
> faster with some xslt optimizations, but I think now we should outline some
> roadmap before we start to prepare patches and so.
Can the Docbook5 build be sped up with similar hacks?
Jürgen Purtz wrote:
> I measured following elapsed times on an Intel i5 processor:
>
> 1. generate all HTML files with dsl script (make html): 0:48 min.
> 2. generate all HTML files with xslt script (make xslthtml): 16:01 min.
> 3. generate all HTML files with xslt script in the new environment
>
Jürgen Purtz wrote:
> Hi,
> actually we use DocBook V4.2 for the PostgreSQL manuals. I suggest an
> upgrade to DocBook 5.x. This sounds simple, but it will be a long process
> with many sub-tasks.
Yes, agreed. The killer objection placed last time was that it took
something like 10x longer to gen
Peter Geoghegan wrote:
> On Thu, Feb 18, 2016 at 4:53 PM, Tom Lane wrote:
> >> there are usage patterns where half-dead pages might accumulate.
> >
> > Other than a usage pattern of "randomly SIGKILL backends every few
> > seconds", I don't see how that would happen.
>
> I meant where pages coul
Jürgen Purtz wrote:
> Recommendations:
>
> * We suggest the use of Inkscape. It creates the above mentioned
>format by performing the following steps
> o File | Clean up document
> o File | Save as | Plain SVG
As in the original discussion, this is probably too fiddly and the
resu
Alvaro Herrera wrote:
> Not sure what is going on; my reading of the code certainly says that
> the data should be there. I'm looking into it.
>
> I also noticed that I didn't actually push the whole of the patch
> yesterday -- I neglected to "git add" the
Robert Haas wrote:
> On Mon, Dec 7, 2015 at 8:33 AM, Fujii Masao wrote:
> > So firstly you will push those "latest" changes soon?
>
> It seems like these changes haven't been pushed yet, and unfortunately
> that's probably a beta blocker.
I'm on this.
--
Álvaro Herrerahttp://w
Fujii Masao wrote:
> Sorry for not reviewing the patch before you push it...
>
> In HEAD, I ran very simple test case:
>
> 1. enable track_commit_timestamp
> 2. start the server
> 3. run some transactions
> 4. execute pg_last_committed_xact() -- returns non-null values
> 5. shutdown the server w
Petr Jelinek wrote:
> While this seems good, I'd code it slightly differently. I didn't like the
> addition of new bool when it's not really needed. This brings the question
> if we actually need the BootStrapCommitTs and StartupCommitTs functions
> which really don't do much though.
Thanks, it's
I paraphrase Fujii Masao, who wrote:
> 1. Start the master and standby servers with track_commit_timestamp enabled.
> 2. Disable track_commit_timestamp in the master and restart the master server.
> 3. Run checkpoint in the master.
> 4. Run restartpoint in the standby after the checkpoint WAL reco
Anastasia Lubennikova wrote:
> Fix incomplete gist interface description.
Hi, thanks for the patch.
I think this sentence is a bit confusing:
>
> - GiST indexes require seven support functions, with an optional eighth, as
> + GiST indexes require seven support functions, with two optiona
Alvaro Herrera wrote:
> Robert Haas wrote:
> > On Sat, Oct 17, 2015 at 5:37 PM, Petr Jelinek wrote:
> > > I agree with that sentiment.
> > >
> > > Attached patch adds variable to the shmem which is used for module
> > > activation tracking -
Robert Haas wrote:
> On Sat, Oct 17, 2015 at 5:37 PM, Petr Jelinek wrote:
> > I agree with that sentiment.
> >
> > Attached patch adds variable to the shmem which is used for module
> > activation tracking - set to true in ActiveCommitTs() and false in
> > DeactivateCommitTs(). All the checks insi
Robert Haas wrote:
> The standby can have the feature enabled even though the master has it
> disabled? That seems like it can only lead to heartache.
Can you elaborate?
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Se
x7 Support, Remote DBA, Training & Services
commit 7441f88b746b7522f1714ed9fec95c3c4fe1dacb[m
Author: Alvaro Herrera
AuthorDate: Fri Oct 2 11:39:44 2015 -0300
CommitDate: Fri Oct 2 11:39:44 2015 -0300
Don't disable commit_ts in standby if enabled locally
Bug noticed by Fujii
Fujii Masao wrote:
> I've not read the patch yet, but the patched server with
> track_commit_timestamp
> enabled caused the following PANIC error when I ran pgbench.
Ah, that was a stupid typo: I used || instead of &&. Fixed that.
I also changed DeactivateCommitTs() so that it removes all slru
oonish...@nttdata.co.jp wrote:
> The below error messages were shown in standby server log:
>
> FATAL: could not access status of transaction 9009
> DETAIL: Could not read from file "pg_commit_ts/" at offset 90112:
> Success.
> CONTEXT: xlog redo Transaction/COMMIT: 2015-09-30 15:52:41.92
Adding CC to hackers, since this is clearly not just a docs issue. Also
CCing Petr and Craig since they are the ones that know how this is used
in BDR.
Robert Haas wrote:
> On Tue, Aug 4, 2015 at 12:41 AM, Alvaro Herrera
> wrote:
> > The alternative is to turn the feature on auto
Robert Haas wrote:
> On Thu, Jul 16, 2015 at 12:07 AM, Fujii Masao wrote:
> > One example which makes me a bit confusing is; both master and
> > standby are running fine with track_commit_timestamp disabled,
> > then I enable it only on the master. That is, the value of
> > track_commit_timestamp
Kevin Grittner wrote:
> Hopefully the example from the Wiki makes it clear. There has been
> some discussion about whether to link to the Wiki or bring an
> example like that into the documentation; but we usually don't
> link to Wiki pages and the example is somewhat long to include
> in-line in
I wrote this a very long time ago but apparently it was eaten by a spam
filter before it reached the lists. Resending.
Craig Ringer wrote:
> From c73d1303cb3474ccc799eeda252eeef1fc3d9026 Mon Sep 17 00:00:00 2001
> From: Craig Ringer
> Date: Mon, 16 Feb 2015 18:17:48 +1300
> Subject: [PATCH 1/4]
I'm sitting in Alexey Ermakov's talk and he just said that the command
in $SUBJECT is not documented ... do we need a separate blurb about it
somewhere?
I just tried it and it does do something useful, at least for expression
indexes, since we collect stats for those. This is news to me. There's
Fujii Masao wrote:
> Hi,
>
> "25.5.3. Administrator's Overview" in the document
> -
> The setting of some parameters on the standby will need reconfiguration
> if they have been changed on the primary. For these parameters,
> the value on the sta
David G. Johnston wrote:
> On Mon, Jun 15, 2015 at 4:58 PM, Euler Taveira wrote:
>
> > On 15-06-2015 13:32, Jeff Janes wrote:
> > > Isn't it unfortunate that the command used for changing the
> > > configuration file from within SQL mentions SIGHUP and pg_ctl
> > > reload, but not "select pg_rel
Fujii Masao wrote:
> Hi,
>
> The descriptions of pg_class.relminmxid and pg_database.datminmxid
> have some minor problems in the doc. Seems the attached patch needs
> to be applied.
Looks reasonable. I'm not sure about the term "multitransaction"
anymore; we use "multixact" elsewhere (notably i
Joshua D. Drake wrote:
> A change I did not make per Craig Ringer (and plenty of other people through
> the years):
>
> "Instead we should be advising people to use pg_dump -Fc and pg_restore as
> their default and primary method of dumping a database. It is rarely
> desirable to use text dumps a
Joshua D. Drake wrote:
>
> On 05/27/2015 06:31 PM, Alvaro Herrera wrote:
> >
> >Joshua D. Drake wrote:
> >>The man page does not clearly state that pg_dump will not dump things like
> >>users or roles. It does mention briefly in the notes section that pg_dump
Joshua D. Drake wrote:
> The man page does not clearly state that pg_dump will not dump things like
> users or roles. It does mention briefly in the notes section that pg_dumpall
> is needed for items that are set via SET but that isn't very clear on the
> other items.
I agree that we need a warni
Dagfinn Ilmari Mannsåker wrote:
> The introduction in the Shared Library Preloading section already
> instructs the user to separate multiple library names with commas, so
> just remove the fragment from here.
>
> --
> "The surreality of the universe tends towards a maximum" -- Skud's Law
> "Neve
Peter Eisentraut wrote:
> The last pgfoundry link in our docs is
>
>
>More example scripts can be found in the PgFoundry
>http://pgfoundry.org/projects/dtrace/";>dtrace
> project.
>
>
> pgfoundry is now pretty much unusable, so we should update this.
>
> Does anyone know whether th
Kevin Grittner wrote:
> In patch 0003- I agree that the change to "exactly the same" reads
> better. I'm torn on changing the hyphens to spaces. I probably
> wouldn't change them, but I wouldn't squawk if others preferred to
> do so.
Apparently adverb hyphenation discussion plagues the web. On
Amit Langote wrote:
> On Thu, Apr 10, 2014 at 10:25 PM, Rob Sargent wrote:
> > And it also tells you how to stop it --bibtex iirc
>
> Yeah, it's a caution against a potentially harmful usage anyway. Users
> should not use it at all.
>
> I was just wondering if the description of the behavior, th
Robert Haas wrote:
> On Tue, Apr 8, 2014 at 4:41 PM, Tom Lane wrote:
> > I just created sections in the SGML manual chapters about GIST, GIN, and
> > SP-GIST to hold documentation about the standard opclasses provided for
> > them:
> >
> > http://www.postgresql.org/docs/devel/static/gist-builtin-o
Peter Eisentraut wrote:
> On 5/31/13 8:46 AM, Thom Brown wrote:
> >> pg_class.relminmxid
> >> > pg_database.datminmxid
> > Could someone add these in?
>
> These are from Álvaro's foreign-key locking patch. Perhaps he can fill
> these in, which an informed description.
Done, thanks.
--
Álvaro H
Tom Lane wrote:
> The underlying bug is allegedly fixed as of TeX Live 2012; can you get
> hold of a newer toolchain?
It fails there as well, I just tried.
$ pdfjadetex
This is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012/Debian)
restricted \write18 enabled.
--
Álvaro Herrera
Jeff Frost wrote:
> On Jun 26, 2013, at 13:20, Alvaro Herrera wrote:
>
> >> Any idea how to fix it?
> >
> > Nope, but maybe try to build the PDF using the XML toolchain?
>
> I'm afraid that's a bit out of my depth. I would speculate that since the US
Jeff Frost wrote:
> Well, happy to hear that I'm not special, but sad to hear that it doesn't
> build. :-/
Agreed on both counts.
> Any idea how to fix it?
Nope, but maybe try to build the PDF using the XML toolchain?
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Dev
Jeff Frost wrote:
> Alvaro, did both the beta2 PDFs build fine on borka? If so, could you get
> them to me so I can build the RPMs while I figure out the issue with my
> tex/jade setup?
I don't think borka builds those PDFs. But I tried locally, and I am
sad to report that it fails here as well
Jeff Frost wrote:
> Yah, it's a different error when it's the wrong openjade version.
>
> It looks like this one that's in the docs:
>
> openjade:./stylesheet.dsl:664:2:E: flow object not accepted by port; only
> display flow objects accepted
> make: *** [postgres-A4.tex-pdf] Segmentation fault
Jeff Frost wrote:
> On 06/26/13 10:34, Jeff Frost wrote:
> > On 06/26/13 10:31, Alvaro Herrera wrote:
> >> Jeff Frost wrote:
> >>
> >>> ! pdfTeX error (ext4): \pdfendlink ended up in different nesting level
> >>> than \pd
> >
Jeff Frost wrote:
> ! pdfTeX error (ext4): \pdfendlink ended up in different nesting level than
> \pd
> fstartlink.
Did you see this one?
http://www.postgresql.org/message-id/3b4139a6e0ceea903dd359b7035d5d4a.squir...@webmail.xs4all.nl
--
Álvaro Herrerahttp://www.2ndQuadrant.c
Tom Lane wrote:
> Magnus Hagander writes:
> > On Thu, Jun 13, 2013 at 3:45 PM, Tom Lane wrote:
> >> Also, FYI, this is claimed to be fixed in TeX Live 2012:
> >> https://bugzilla.redhat.com/show_bug.cgi?id=619481
> >> so a toolchain upgrade is the long-term answer.
>
> > Just to be clear, it's f
Peter Eisentraut wrote:
> On 5/31/13 8:46 AM, Thom Brown wrote:
> >> pg_class.relminmxid
> >> > pg_database.datminmxid
> > Could someone add these in?
>
> These are from Álvaro's foreign-key locking patch. Perhaps he can fill
> these in, which an informed description.
Sorry I missed the thread.
Robins Tharakan escribió:
> Yes, but the documentation states that EXECUTE permission for the function
> is required to even CREATE the operator.
What I mean is that your new role still has said permission through
PUBLIC (a pseudo-role which is automatically granted to all other roles
and cannot b
Robins Tharakan escribió:
> Further, I seem to have a similar problem with the EXECUTE check
> requirement as well.
> Sample SQL given below.
>
> BEGIN TRANSACTION;
> CREATE ROLE rol_op3;
> CREATE TYPE type_op3 AS ENUM ('new', 'open', 'closed');
> CREATE FUNCTION fn_op3(type_op3, type_op3)
> RETUR
Bruce Momjian wrote:
> On Fri, May 3, 2013 at 07:36:09PM -0400, Alvaro Herrera wrote:
> > We do have other files that use underscores, anyway.
>
> Well, we have only four:
>
> generate_history.pl information_schema.sgml mk_feature_tables.pl
> pg_xlogdum
Bruce Momjian wrote:
> I just noticed that pg_xlogdump uses an underscore in the file name,
> pg_xlogdump.sgml, unlike every other extension. Should this be fixed?
I did mess about with hyphens vs. underscores vs. nothing at all. Most
seem to use no char, so "pgrowlocks.sgml" for example, but th
Bruce Momjian wrote:
> I just noticed from the commit logs that Pavel's name is spelled Pavel
> Stěhule. That mark above the e is a caron, and is explained here:
>
> http://en.wikipedia.org/wiki/Caron
> http://en.wikipedia.org/wiki/%C4%9A
>
> Can anyone suggest how to get that into t
Alexander Law escribió:
> Hello,
>
> I have translated into Russian first two parts of the PostgreSQL
> documentation and want to publish my work.
> Can I create app for Google Play Market as an e-book that will
> contain my translation?
> Can I make it paid?
> Should I add some special notices to
Edward Hooper escribió:
> If anyone from O'Reilly Media is on this mailing list please let me know
> how you do this, i.e. what tools you use and what commands you run to
> produce the ePub books that I buy from you.
Would it work to just take the single-page HTML output (make
postgres.html) and
Excerpts from vilpesh's message of jue jul 19 07:47:29 -0400 2012:
> Hi Josh & Stefan,
>
> Download location of postgresql-9.1-US
> http://www.postgresql.org/docs/manuals/
> specifically
> http://www.postgresql.org/files/documentation/pdf/9.1/postgresql-9.1-US.pdf
>
> Details of postgresql-9.1-
Excerpts from Greg Smith's message of lun jul 02 20:30:07 -0400 2012:
> A documentation comment came in recently about ssl-tcp.html not
> specifying what format is expected for the CRL file. Seems like
> something that could be described better now that I look at it, so I'm
> passing that alon
Excerpts from Josh Berkus's message of jue jun 21 18:53:06 -0400 2012:
>
> > 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;
Excerpts from Peter Eisentraut's message of mar abr 17 14:40:37 -0300 2012:
> It occurred to me that it could be useful to separate the information
> about which privileges are necessary for a certain SQL command into a
> separate section "Privileges" on each SQL command reference page.
> Currentl
Excerpts from Greg Sabino Mullane's message of mié mar 28 16:51:06 UTC 2012:
>
> Hash: RIPEMD160
>
> > What I would love love LOVE to see would be a dropdown by the
> > "Home â Documentation â Manuals â PostgreSQL 8.3" where I'm
> > able to choose from other versions easily. Or maybe it will
Excerpts from Marti Raudsepp's message of vie mar 16 07:08:18 -0300 2012:
> On Sat, Mar 3, 2012 at 02:16, Marti Raudsepp wrote:
> > The documentation needs some updates now that we have index-only
> > scans.
>
> Bump. No response for 2 weeks. Anyone?
Add it here:
http://wiki.postgresql.org/wiki
Excerpts from John Lumby's message of mié mar 14 10:25:19 -0300 2012:
>
> On 12-01-2012 17:28, Josh Berkus wrote:
>
> > Can't open perl script "/bin/collateindex.pl": No such file or directory
>
> On Thu, 12 Jan 2012 19:37:20 -0300 Alvaro Herrera wrote
Excerpts from Tom Lane's message of jue ene 12 18:55:41 -0300 2012:
> Josh Berkus writes:
> > 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
>
> On Fedora, that scrip
Excerpts from Josh Berkus's message of jue ene 12 18:43:39 -0300 2012:
>
> > The warning about "unknown warning type" means you're using the wrong
> > tool to me. My toolchain here uses "openjade" which is a fork of the
> > earlier jade (so install opensp as Kevin suggested, and rerun configure
Excerpts from Josh Berkus's message of jue ene 12 17:28:28 -0300 2012:
> 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'
> { \
> echo ""; \
> echo "
Excerpts from Erik Rijkers's message of vie dic 16 19:04:06 -0300 2011:
> Here are two small changes to mvcc.sgml:
>
> 1. typo ('are' for 'at')
>
> 2. Change title of Table 13.1 to say 'Standard SQL' instead of just 'SQL', to
> make immediately
> clear that the table does /not/ show the levels
Excerpts from Bruce Momjian's message of lun dic 12 22:45:20 -0300 2011:
> I just tried to build our docs on Debian Squeeze using our instructions
> for Debian:
>
> http://www.postgresql.org/docs/9.1/static/docguide-toolsets.html
> apt-get install docbook docbook-dsssl docbook-xsl openjad
Excerpts from Stefan Kaltenbrunner's message of jue nov 24 17:45:07 -0300 2011:
>
> On 11/24/2011 09:16 PM, Alvaro Herrera wrote:
> > # ldap support is new as of 8.2
> > if ($branch eq 'HEAD' || $branch ge 'REL8_2')
>
> this basically means
1 - 100 of 335 matches
Mail list logo
