| From: | Vadim Mikheev <vadim(at)krs(dot)ru> |
|---|---|
| To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, t-ishii(at)sra(dot)co(dot)jp, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] Open 6.5 items |
| Date: | 1999-05-31 01:41:55 |
| Message-ID: | 3751E8E3.A20A7393@krs.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hiroshi Inoue wrote:
>
> As far as I see,different entries in xidHash have a same key when above
> case occurs. Moreover xidHash has been in abnormal state since the
> number of xidHash entries exceeded 256.
>
> Is this bug solved by change maxBackends->NLOCKENTS(maxBackends)
> by Vadim or the change about hash by Tom ?
Should be fixed now.
>
> As for my test case,xidHash is filled with XactLockTable entries which have
> been acquired by XactLockTableWait().
> Could those entries be released immediately after they are acquired ?
Ops. Thanks! Must be released.
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Colin McCormack | 1999-05-31 01:44:47 | Announcement - SWIG based tcl interface (with asynch query) |
| Previous Message | Hiroshi Inoue | 1999-05-31 01:36:45 | RE: [HACKERS] Open 6.5 items |