Log Message:
---
Initial release of changes for serialisation. All session variables
are now serialisable. Still need to do serialisation of the session
as a whole. Also comments are needed but regression tests look good.
Modified Files:
--
veil/demo:
funcs.sql
Magnus Hagander wrote:
> Tom Lane wrote:
> > According to what you just told me, the original coding is storing the
> > name in a "local namespace", which presumably means it won't conflict
> > anyway. Ergo, the existing coding is simply broken and there's nothing
> > we can do about it.
>
> Loc
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> Heikki Linnakangas wrote:
>>> What happens if someone launches version 8.3.3 postgres.exe and version
>>> 8.3.4 postgres.exe at the same time, on the same data directory? Will
>>> the interlock that prevents two postmasters from start
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Heikki Linnakangas wrote:
>> What happens if someone launches version 8.3.3 postgres.exe and version
>> 8.3.4 postgres.exe at the same time, on the same data directory? Will
>> the interlock that prevents two postmasters from starting at the same
>> tim
Log Message:
---
[#1010424] French localization
Added French localization. Thanks Mathieu Cartoixa (mathieu.cartoixa @nospam@
free.fr) for patch.
Modified Files:
--
Npgsql2/src:
Npgsql.build (r1.13 -> r1.14)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npg
Log Message:
---
The version is now 8.3.0201.
1. SQLGUID type support thanks to Jan-Willem Goossens.
2. Fix a bug about silently adding a *for read only* clause.
3. Fix a 64bit mode bug about handling of arrays of parameters.
4. Change the implemetatin of SQLForeignKeys() for 8.3+ servers.
Log Message:
---
Fix initialization of GinScanEntryData.partialMatch
Modified Files:
--
pgsql/src/backend/access/gin:
ginscan.c (r1.15 -> r1.16)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginscan.c?r1=1.15&r2=1.16)
--
Sent via
Magnus Hagander wrote:
Heikki Linnakangas wrote:
Magnus Hagander wrote:
Fix a couple of bugs in win32 shmem name generation:
* Don't cut off the prefix. With this fix, it's again readable.
* Properly store it in the Global namespace as intended.
Tags:
REL8_3_STABLE
What happens if someon
Heikki Linnakangas wrote:
> Magnus Hagander wrote:
>> Log Message:
>> ---
>> Fix a couple of bugs in win32 shmem name generation:
>> * Don't cut off the prefix. With this fix, it's again readable.
>> * Properly store it in the Global namespace as intended.
>>
>> Tags:
>>
>> REL8_3_STAB
Magnus Hagander wrote:
Log Message:
---
Fix a couple of bugs in win32 shmem name generation:
* Don't cut off the prefix. With this fix, it's again readable.
* Properly store it in the Global namespace as intended.
Tags:
REL8_3_STABLE
What happens if someone launches version 8.3.3
Log Message:
---
Fix a couple of bugs in win32 shmem name generation:
* Don't cut off the prefix. With this fix, it's again readable.
* Properly store it in the Global namespace as intended.
Modified Files:
--
pgsql/src/backend/port:
win32_shmem.c (r1.4 -> r1.5)
Log Message:
---
Fix a couple of bugs in win32 shmem name generation:
* Don't cut off the prefix. With this fix, it's again readable.
* Properly store it in the Global namespace as intended.
Tags:
REL8_3_STABLE
Modified Files:
--
pgsql/src/backend/port:
win32_
12 matches
Mail list logo
