"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Alvaro Herrera <[EMAIL PROTECTED]> wrote:
>> The point is that archive.org will keep that copy online even if
>> hp.com decides to shut it down or change it.
> There is a question to the legality of the archive.org copy. The legal
> notice of the doc
Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
The point is that archive.org will keep that copy online even if
hp.com decides to shut it down or change it.
There is a question to the legality of the archive.org copy. The legal
notice
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> The main problem with using the link as it stands is that it is *highly*
> >> unlikely that it will remain valid for the lifespan of the PG 8.3
> >> documentation (let alone subsequent versions). I've been dealing
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> The main problem with using the link as it stands is that it is *highly*
>> unlikely that it will remain valid for the lifespan of the PG 8.3
>> documentation (let alone subsequent versions). I've been dealing with
> Did you see Alvar
Tom Lane wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> > Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> >> The point is that archive.org will keep that copy online even if
> >> hp.com decides to shut it down or change it.
>
> > There is a question to the legality of the archive.org copy. T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 31 Jan 2008 20:18:27 -0300
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Bruce Momjian wrote:
> > Alvaro Herrera wrote:
>
> > > If you really like that page, you could link to archive.org's
> > > version of it:
> > >
> > > http://web.archive.o
Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > I looked at the SSL docs and they are _minimal_:
> >
> > http://www.openssl.org/docs/
> >
> > In fact "[STILL INCOMPLETE]" is on almost every item.
> >
> > > appropriate. We're not here to substitute for somebody doing their
> > > own Google s
Bruce Momjian wrote:
> I looked at the SSL docs and they are _minimal_:
>
> http://www.openssl.org/docs/
>
> In fact "[STILL INCOMPLETE]" is on almost every item.
>
> > appropriate. We're not here to substitute for somebody doing their
> > own Google search ...
>
> The HP page is not a prima
Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > If you really like that page, you could link to archive.org's version of
> > it:
> >
> > http://web.archive.org/web/20060903180210/http://h71000.www7.hp.com/DOC/83final/BA554_90007/ch04s02.html
>
>
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> >>> Furthermore HP is hardly the authoritative reference on SSL. Can't
> >>> we find an RFC or something?
> >>
> >> See above.
>
> > If anything, we should link to OpenSSL, because they implement the API we
> > are
> > referring t
Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > True, and Magnus was concerned about that as well. What I liked about
> > it was the diagrams which I haven't seen anywhere else. Our doc
> > reference is:
> >
> > (See http://h71000.www7.hp.com/DOC/83final/BA554_90007/ch04s02.html for
> >
Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > True, and Magnus was concerned about that as well. What I liked about
> > it was the diagrams which I haven't seen anywhere else. Our doc
> > reference is:
> >
> > (See http://h71000.www7.hp.com/DOC/83final/BA554_90007/ch04s02.html for
> >
I wrote:
> This is exactly *not* what I wanted to do, as it removes all traces
> of knowledge about which platforms are likely to work (or not work)
> despite not being represented in the current buildfarm. It also
> seems a bit silly to copy-and-paste today's buildfarm roster into
> static docume
On Jan 31, 2008 5:29 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Christopher Browne" <[EMAIL PROTECTED]> writes:
> > Attached is a patch.
>
> > I have changed the discussion to focus on the buildfarm process, and
> > it should be recognized that this does change the "shape" of how this
> > section r
On Jan 31, 2008 5:35 PM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, 31 Jan 2008 12:29:05 -0500
> Tom Lane <[EMAIL PROTECTED]> wrote:
>
> > Can't speak to Slackware or Irix, but IMHO Fedora and HP/UX deserve to
>
> I know of at least one
Bruce Momjian wrote:
> True, and Magnus was concerned about that as well. What I liked about
> it was the diagrams which I haven't seen anywhere else. Our doc
> reference is:
>
> (See http://h71000.www7.hp.com/DOC/83final/BA554_90007/ch04s02.html for
> diagrams showing SSL certific
Peter Eisentraut <[EMAIL PROTECTED]> writes:
>>> Furthermore HP is hardly the authoritative reference on SSL. Can't
>>> we find an RFC or something?
>>
>> See above.
> If anything, we should link to OpenSSL, because they implement the API we are
> referring to. I don't know what HP has to do wi
Am Donnerstag, 31. Januar 2008 schrieb Bruce Momjian:
> I put it in parentheses to highlight the URL is only for reference to
> the diagrams and explaination. We can either remove the URL or remove
> it if the URL changes.
>
> SSL is pretty complicated so when I saw something that made it clearer,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 31 Jan 2008 12:29:05 -0500
Tom Lane <[EMAIL PROTECTED]> wrote:
> Can't speak to Slackware or Irix, but IMHO Fedora and HP/UX deserve to
I know of at least one core member who hearts Slackware. :)
Joshua D. Drake
- --
The PostgreSQL Compan
"Christopher Browne" <[EMAIL PROTECTED]> writes:
> Attached is a patch.
> I have changed the discussion to focus on the buildfarm process, and
> it should be recognized that this does change the "shape" of how this
> section recognizes platforms as being "supported."
This is exactly *not* what I
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> PQinitSSL *is* documented, though looking at the para immediately raises
> >> the question what the heck we are doing pointing to a random hp.com page
> >> for SSL documentation.
>
> > I added that for 8.3. The H
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> PQinitSSL *is* documented, though looking at the para immediately raises
>> the question what the heck we are doing pointing to a random hp.com page
>> for SSL documentation.
> I added that for 8.3. The HP documentation seemed excelle
On Jan 30, 2008 11:00 PM, Christopher Browne <[EMAIL PROTECTED]> wrote:
> On Jan 30, 2008 9:59 PM, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> > So someone will need to update that list very soon then. I don't think we
> > can
> > release it as is.
>
> Howbeit I'll see about grabbing the existi
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > I disagree. I think PQinitSSL is meant to be called from the
> > application, for example. Same with PQsetClientEncoding. And the
> > PQExpBuffer stuff is all very useful, and years ago when I wrote an app
> > to use it it annoyed
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I disagree. I think PQinitSSL is meant to be called from the
> application, for example. Same with PQsetClientEncoding. And the
> PQExpBuffer stuff is all very useful, and years ago when I wrote an app
> to use it it annoyed me that there were no docs
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Pavel Golub wrote:
> > > Hello, pgsql-docs.
> > >
> > > I noticed that some exported functions are not documented in the
> > > Chapter 30. However, there are some info about them in other chapters,
> > > e.g. PQclientEncoding using is described in c
Bruce Momjian wrote:
> Pavel Golub wrote:
> > Hello, pgsql-docs.
> >
> > I noticed that some exported functions are not documented in the
> > Chapter 30. However, there are some info about them in other chapters,
> > e.g. PQclientEncoding using is described in chapter 22.2.3 "Automatic
> > Charact
Pavel Golub wrote:
> Hello, pgsql-docs.
>
> I noticed that some exported functions are not documented in the
> Chapter 30. However, there are some info about them in other chapters,
> e.g. PQclientEncoding using is described in chapter 22.2.3 "Automatic
> Character Set Conversion Between Server an
Hello, pgsql-docs.
I noticed that some exported functions are not documented in the
Chapter 30. However, there are some info about them in other chapters,
e.g. PQclientEncoding using is described in chapter 22.2.3 "Automatic
Character Set Conversion Between Server and Client".
This is the list of
29 matches
Mail list logo
