The following bug has been logged online:
Bug reference: 1649
Logged by: Nicholas Vinen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Gentoo Linux
Description:Date calculation year off-by-one error
Details:
This is definitely not right
hello dear postgresql,
I have download postgresql-8.0.2 in order to use it.
But Not work due that some dll are missing in the zip file of postgresql-8.0.2.
example : libeay32.dll, ssleay32.dll.
I have download both of them, but still postgresql doesn't work
because some entry in the ddl's are mi
Boris van Schooten <[EMAIL PROTECTED]> writes:
> Looks good to me. I'd prefer to have a warning message (if (verbose)
> fprintf stderr) for each of the exceptional conditions though. I'm even
> so paranoid I prefer to have the verbose switch on by default.
Don't really see the need for it. What
The following bug has been logged online:
Bug reference: 1647
Logged by: Dirk Bade
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: SUSE LINUX 7.3
Description:shows version 7.1, doesnt create tablespaces etc.
Details:
postgresql-8.0.1.tar
The following bug has been logged online:
Bug reference: 1650
Logged by: Nicholas Vinen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.2
Operating system: Gentoo Linux
Description:Upgraded postgres, problem went away
Details:
8.0.2 is not marked as "stable
Looks good to me. I'd prefer to have a warning message (if (verbose)
fprintf stderr) for each of the exceptional conditions though. I'm even
so paranoid I prefer to have the verbose switch on by default.
Kinds regards,
Boris van Schooten
On Wed, 4 May 2005, Tom Lane wrote:
> Boris van Schooten
The following bug has been logged online:
Bug reference: 1648
Logged by: Nicholas Vinen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Gentoo Linux
Description:ISO Year ignores time zone?
Details:
rt3=# SELECT to_char(timestamp with tim
"Nicholas Vinen" <[EMAIL PROTECTED]> writes:
> This is definitely not right:
> rt3=# SELECT date_trunc('week', timestamp with time zone '2005-01-02
> 00:00:00-7');
>date_trunc
>
> 2006-01-02 00:00:00-08
> (1 row)
Already fixed in 8.0.2.
On Wed, May 04, 2005 at 05:21:13PM +0100, Dirk Bade wrote:
>
> postgresql-8.0.1.tar.gz installs fine and tests run ok. But after initdb
> PG_VERSION shows 7.1 and simple commands like CREATE TABLESPACE or ALTER
> TABLE return errors. What's wrong ?
It sounds like you've installed 8.0.1 but are ru
"Dirk Bade" <[EMAIL PROTECTED]> writes:
> postgresql-8.0.1.tar.gz installs fine and tests run ok. But after initdb
> PG_VERSION shows 7.1 and simple commands like CREATE TABLESPACE or ALTER
> TABLE return errors. What's wrong ?
You're still talking to a 7.1 postmaster.
reg
"Nicholas Vinen" <[EMAIL PROTECTED]> writes:
> rt3=# SELECT to_char(timestamp with time zone '2003-12-31 14:44:44-08', 'Mon
> IYYY');
> to_char
> --
> Dec 2004
> (1 row)
I believe that's correct. 2003-12-31 falls into the first week of ISO 2004.
regards, tom l
Jason Erickson wrote:
> Taken from microsoft at:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock/win
> sock/wsastartup_2.asp
> ---
> An application must call one WSACleanup call for every successful WSAStartup
> call to
Bruce Momjian writes:
> I agree freePGconn() is the proper place. I will apply the following
> patch to current CVS and to 8.0.X. 8.0.3 is being packaged now so I
> will wait for 8.0.4.
Go ahead and put it in --- I'll wait for your commit.
regards, tom lane
---
Bruce Momjian writes:
> Jason Erickson wrote:
>> The only place WSACleanup is being called is libpqdll when the process
>> detaches the DLL (if the libpq is not staticly linked in), which matches up
>> with the WSAStartup when the process attaches to the DLL.
>>
>> The WSAStartup in the fe-connec
>>> The only place WSACleanup is being called is libpqdll when
>the process
>>> detaches the DLL (if the libpq is not staticly linked in),
>which matches up
>>> with the WSAStartup when the process attaches to the DLL.
>>>
>>> The WSAStartup in the fe-connect.c->makeEmptyPGconn() does
>not have
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> Actually ... why do we need a WSAStartup in makeEmptyPGconn?
>> If we have one in DLL attach, isn't that sufficient?
> Not if you link libpq as a static lib...
> I *think* that's why it was added. In the beginning it was only in the
> DLL attach
Tom Lane wrote:
> Bruce Momjian writes:
> > Jason Erickson wrote:
> >> The only place WSACleanup is being called is libpqdll when the process
> >> detaches the DLL (if the libpq is not staticly linked in), which matches up
> >> with the WSAStartup when the process attaches to the DLL.
> >>
> >> T
Magnus Hagander wrote:
> >>> The only place WSACleanup is being called is libpqdll when
> >the process
> >>> detaches the DLL (if the libpq is not staticly linked in),
> >which matches up
> >>> with the WSAStartup when the process attaches to the DLL.
> >>>
> >>> The WSAStartup in the fe-connect
Tom Lane wrote:
> "Magnus Hagander" <[EMAIL PROTECTED]> writes:
> >> Actually ... why do we need a WSAStartup in makeEmptyPGconn?
> >> If we have one in DLL attach, isn't that sufficient?
>
> > Not if you link libpq as a static lib...
>
> > I *think* that's why it was added. In the beginning it
This has now been packpatched to 8.0.3 and 7.4.X and will be released in
the next few days.
---
Jason Erickson wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1545
> Logged by: Jason E
20 matches
Mail list logo