On Sun, 2004-09-05 at 14:37, Wes wrote:
> System: Mac OS X 10.3.5
> Pg: 8.0.0 b2
Thanks for the report. This is a known issue (it's nothing to worry
about).
-Neil
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PRO
> Operating system: Windows 2000 SP3
>
> Description:Account problems-start as a service
> option install
> Windows 2000/ XP
>
> Details:
>
> Problems with installer (for Version 8.0 Beta 2 dev 3) when
> you check the 'Install as a service' checkbox.
>
> Installer cheerfully cre
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> Description:returns different result for the same result with
> differnt plans.
> I ran the query with enable_mergejoin set to on/off, the results are
> different. Postgres chose Merge Left Join when enable_mergejoin is on and
> Hash
Mark Shewmaker <[EMAIL PROTECTED]> writes:
> (BTW, I had sent my first reply and this privately as I'm far from sure
> of myself in these questions, so but feel free to reply to either
> publicly if you want to, or I can re-reply publicly.)
cc'd to pgbugs in case anyone else is wondering the same.
The following bug has been logged online:
Bug reference: 1257
Logged by: stig
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 Beta
Operating system: all
Description:add support for 1-byte integer and 4-bit integer
Details:
hello, i could not find this
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> for the next version of postgresql i would like to see support for 1-byte
> integers (signed and unsigned) and also for 4-bit (1/2-byte) integers
> (signed and unsigned).
See the "char" type (not to be confused with char(n)) and the bitstring
PostgreSQL Bugs List wrote:
> why is this feature important?
> having in mind the development of datawarehouses with huge amount of
> data (hundreds of millions, or billions of rows in fact tables) every
> byte is of importance.
Yet how many applications could make use of the limited range that a
The following bug has been logged online:
Bug reference: 1258
Logged by: Vadim Passynkov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.5
Operating system: FreeBSD 4.10-STABLE
Description:backend memory leak after massive 'CREATE/DROP USER'
Details:
Description:backend memory leak after massive 'CREATE/DROP USER'
wild guess says that its not really neccessarily a memory leak unless all
the shared_buffers are getting consumed and its *still* growing...
CREATE USER adds a row to a system table, and DROP USER deletes that row,
the tabl
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> Description:backend memory leak after massive 'CREATE/DROP USER'
Actually postmaster memory leak, but good catch anyway --- thanks!
The patch against 7.4 is
Index: hba.c
==
10 matches
Mail list logo