Re: [HACKERS] IANA registration

2001-05-04 Thread Bruce Momjian
Did we get anywhere with this? PostgreSQL typically uses port 5432 for client-server communications. It would be a good idea to register this with IANA. This will help to avoid a clash with other services that might try to use the port. DB2, Interbase, MS SQL, MySQL, Oracle, Sybase, etc.

Re: [HACKERS] IANA registration

2001-03-27 Thread Tom Lane
Pete Forman [EMAIL PROTECTED] writes: PostgreSQL typically uses port 5432 for client-server communications. It would be a good idea to register this with IANA. This will help to avoid a clash with other services that might try to use the port. Might someone with a reasonable grasp of the low

Re: [HACKERS] IANA registration

2001-03-27 Thread Tom Lane
The Hermit Hacker [EMAIL PROTECTED] writes: This seemed like a Marc job to me. Marc? Will do ... *nod* Ok, fine here. BTW, I was thinking that rather than filling in their webform in any detail, it'd make the most sense to just supply a link to our protocol documentation, presently

Re: [HACKERS] IANA registration

2001-03-27 Thread Vince Vielhaber
On Tue, 27 Mar 2001, Tom Lane wrote: Vince Vielhaber [EMAIL PROTECTED] writes: Maybe we should arrange for a more stable path to the "current release" docs, ie a symlink without a version number? But there is... http://www.postgresql.org/docs/special/protocol.html No, that's just

[HACKERS] IANA registration

2001-03-26 Thread Pete Forman
PostgreSQL typically uses port 5432 for client-server communications. It would be a good idea to register this with IANA. This will help to avoid a clash with other services that might try to use the port. DB2, Interbase, MS SQL, MySQL, Oracle, Sybase, etc. are already registered. Might someone