Bruce Momjian writes:
> Mark Stosberg wrote:
>> Is that any concern that over time newer pg_restore's won't read old
>> "custom" formats? That would be my only worry-- that the data would be
>> locked in a binary format which becomes unsupported.
> No, we wouldn't do that.
Right, I can't imagine
Mark Stosberg wrote:
> >> Also, I would like it if the pg_dump docs more assertively recommended
> >> one of the "tar" or "custom" formats. They seem very similiar.
> >
> > Yeah. I think it should specifically recommend custom format. The only
> > reason for using tar format would be if you want
On 2006-05-03, Tom Lane <[EMAIL PROTECTED]> wrote:
> Mark Stosberg <[EMAIL PROTECTED]> writes:
>> A suggested addition to the pg_dump docs:
>> This would be an extension to the documentation for the "tar" format:
>
>> The tar format needs some space to create temporary files. By default
>> "/tmp" i
2006/5/9, Peter Eisentraut <[EMAIL PROTECTED]>:
Bruce Momjian wrote:
> Should we modify the doc build process to generate XML and convert
> that to PDF, or allow it as an option, because PDF generation has
> always been a problem from SGML (very slow)?
If the FOP-based build works better than Ja
Bruce Momjian wrote:
> Should we modify the doc build process to generate XML and convert
> that to PDF, or allow it as an option, because PDF generation has
> always been a problem from SGML (very slow)?
If the FOP-based build works better than Jade, by all means let's use
that. Last time I loo
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I have a counter-question. What value is there in continuing to use
> SGML?
We're already used to it, and it's not clear what we'd buy from the
effort of converting all our documentation.
regards, tom lane
Am Dienstag, 9. Mai 2006 13:40 schrieb Alvaro Herrera:
> I have a counter-question. What value is there in continuing to use
> SGML?
Tag reduction makes editing easier (for some).
There's the question whether all the files should be renamed to .xml.
Marked sections would need to be replaced wit
Am Dienstag, 9. Mai 2006 14:00 schrieb Guillaume Lelarge:
> How do you take care of the columns' size in a table ? I use this :
>
> But I don't know if there is the same thing in SGML.
DocBook is DocBook. It doesn't matter if it's written in SGML or XML.
--
Peter Eisentraut
http://developer.
2006/5/9, Peter Eisentraut <[EMAIL PROTECTED]>:
Am Dienstag, 9. Mai 2006 11:19 schrieb Guillaume Lelarge:
> If someone wants to work on sgml/jade/dsssl stylesheets to fix the
> issues I talked earlier, great, good news. But I haven't seen anyone
> talking about this. So perhaps, the good way to h
Peter Eisentraut wrote:
> Am Dienstag, 9. Mai 2006 11:19 schrieb Guillaume Lelarge:
> > If someone wants to work on sgml/jade/dsssl stylesheets to fix the
> > issues I talked earlier, great, good news. But I haven't seen anyone
> > talking about this. So perhaps, the good way to handle this is to g
Am Dienstag, 9. Mai 2006 11:19 schrieb Guillaume Lelarge:
> If someone wants to work on sgml/jade/dsssl stylesheets to fix the
> issues I talked earlier, great, good news. But I haven't seen anyone
> talking about this. So perhaps, the good way to handle this is to go
> the xml way.
I don't think
2006/5/9, Peter Eisentraut <[EMAIL PROTECTED]>:
Guillaume LELARGE wrote:
> The PDF manual available on the postgresql web site is quite
> difficult to use. For example, take a look at table 9.5 (pages 125
> and 126). Text goes beyond the cells. It's really difficult to read
> it. Sometimes you ca
12 matches
Mail list logo
