Hi guys,
BTW, I found the work_mem is still limited to 2GB.
If we support 64bit shared memory, we also need to support
64bit work_mem.
Thanks.
--
NAGAYASU Satoshi <[EMAIL PROTECTED]>
---(end of broadcast)---
TIP 3: Have you checked our extensi
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> On Fri, Jul 08, 2005 at 09:38:07AM +0900, ITAGAKI Takahiro wrote:
>> Avoiding overheads, can XIDs/CIDs be different bit length? For example,
>> can XIDs/CIDs be changed to 48/16-bit or 40/24-bit?
> Not unless you change the definition of HeapTupleFields
On Fri, Jul 08, 2005 at 09:38:07AM +0900, ITAGAKI Takahiro wrote:
> Hans-J|rgen Schvnig <[EMAIL PROTECTED]> wrote:
>
> > 64-bit XIDs seem to be an overkill - the only practical impact I can see
> > is an even larger tuple header (this can be an issue on large boxes too
> > - at least compare
On Thu, Jul 07, 2005 at 06:23:40PM +0200, Hans-Jürgen Schönig wrote:
> Tom Lane wrote:
> >Koichi Suzuki <[EMAIL PROTECTED]> writes:
> >
> >>Here're a couple of patches for PostgreSQL 64bit support. There're just
> >>two extension to 64bit, size of shared memory and transaction ID.
> >
> >
> >I ask
