> >OK ... are you supposed to find it out by looking at the environment
> >vars, or is there another API defined?
> >
> >I am planning to consolidate the platform dependency into a function
> >defined like
> >
> > static bool pqGetHomeDirectory(char *buf, int bufsize)
> > {
> >
> The following bug has been logged online:
>
> Bug reference: 1372
> Logged by: Graham Robson
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0
> Operating system: Windows XP SP2
> Description:Service won't start with tcpip_socket = true
> Details:
>
> Tr
Title: File Groups with postgresql
I'm not sure if this is the right forum for this question, but here goes.
I am trying to create a database with a preallocated amount of storage (eg. Filegroups in SQL Server).
Is this possible with postgresql or is there an equivalent.
Gareth Segree
mail
Thanks. Updated.
---
Tanel Hiir wrote:
>
> Stumbled over two broken links in Developer's Frequently Asked Questions
> (rev=1.78).
>
> Document heading contains:
> http://www.PostgreSQL.org/docs/faqs/FAQ_DEV.html
> shoul
On Tue, 4 Jan 2005, Graham Robson wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1372
> Logged by: Graham Robson
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0
> Operating system: Windows XP SP2
> Description:Service won't sta
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> Tom also wrote:
>> Now that I look at it, there are several places that are depending on
>> getenv("HOME") or getenv("USERPROFILE") (on Windows) as the meaning of
>> "home directory". In particular ~/.pgpass is sought there, and psql
>> also uses get
Tom Lane wrote:
> I wrote:
> > win32 hackers, anyone know why it's like this?
>
> Looking through the code, it seems that it's because someone thought
> that breaking SSL would be easier than replacing the pqGetpwuid() calls
> that are used to find out the user's home directory.
>
I think what h
> > > win32 hackers, anyone know why it's like this?
> >
> > Looking through the code, it seems that it's because
> someone thought
> > that breaking SSL would be easier than replacing the pqGetpwuid()
> > calls that are used to find out the user's home directory.
> >
>
> I think what happene
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> I think it's only broken when you fiddle with certificates.
Yeah, the commented-out stuff had to do with certificates, and would not
be executed unless the server demands a client certificate (which only
happens if the server has a root.crt file).
B
Tom Lane wrote:
BTW, as of CVS tip, if the server has a root.crt file and the client
does not have any certificate files, the default behavior is that
connections fail:
$ psql -h localhost regression
psql: could not open certificate file "/home/tgl/.postgresql/postgresql.crt":
No such file or dire
Tom Lane wrote:
> "Matthew T. O'Connor" writes:
> > Tom Lane wrote:
> >> Does Windows even have a concept of home directory? What would be a
> >> reasonable equivalent to ~/.postgresql/ ?
>
> > The versions of windows that the port supports (NT4, 2000, 2003, XP) do
> > have home directories.
>
Oliver Jowett <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I'm not sure if this is desirable. Should libpq try to fall back to a
>> non-SSL-encrypted connection, instead?
> Only if the server certificate validates, otherwise an active attacker
> could intercept the SSL connection to force li
Tom Lane wrote:
Basically my point here is that the default "prefer" SSL mode
effectively becomes "require" if the server has a root.crt.
Ok, in the scenario where validation is important, clients should be
using "require" anyway, so it's not an issue so long as libpq doesn't
try to fall back to
13 matches
Mail list logo
