Kurt Roeckx <[EMAIL PROTECTED]> writes:
> If that really was the error you got, your patch couldn't have
> fixed it since it didn't change anything that has something to do
> with it.
I entirely concur with Kurt's observation.
My bet is you got the "no space left on device" failure because you we
creating template1 database in
/export/home/tbaden/posttemp/postgresql-7.4/src/test/regress/./tmp_check/data/b+ase/1...
FATAL: could not create semaphores: No space left on device
DETAIL: Failed system call was semget(1, 17, 03600).
HINT: This error does *not* mean that you have run out of disk
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> Kurt Roeckx <[EMAIL PROTECTED]> writes:
> > He seems to have changed this too:
> > - typedef uint32 IpcMemoryKey;
> > + typedef size_t IpcMemoryKey;
> > That really should be a key_t.
>
> Yeah, I made it key_t in CVS tip. I'm just
> wondering what this co
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> He seems to have changed this too:
> - typedef uint32 IpcMemoryKey;
> + typedef size_t IpcMemoryKey;
> That really should be a key_t.
Yeah, I made it key_t in CVS tip. I'm just wondering what this could
avoid other than possibly a compile warning.
On Mon, Dec 01, 2003 at 06:08:06PM -0500, Tom Lane wrote:
> Kurt Roeckx <[EMAIL PROTECTED]> writes:
> > On Mon, Dec 01, 2003 at 05:19:17PM -0500, Tom Lane wrote:
> >> After reviewing the proposed patch, I find it hard to believe that the
> >> patch would have fixed any such problem ---
>
> > It's
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> On Mon, Dec 01, 2003 at 05:19:17PM -0500, Tom Lane wrote:
>> After reviewing the proposed patch, I find it hard to believe that the
>> patch would have fixed any such problem ---
> It's not the key (key_t) that is the problem, but the size, which
> used to
On Mon, Dec 01, 2003 at 05:19:17PM -0500, Tom Lane wrote:
> Thomas Baden <[EMAIL PROTECTED]> writes:
> > Hi there. My install was failing the regression tests
> > due to a shared memory error.
>
> After reviewing the proposed patch, I find it hard to believe that the
> patch would have fixed any
Thomas Baden <[EMAIL PROTECTED]> writes:
> Hi there. My install was failing the regression tests
> due to a shared memory error.
After reviewing the proposed patch, I find it hard to believe that the
patch would have fixed any such problem --- even if key_t is 64 bits
on your system, the code sho
We have applied a variant of this to CVS. Thanks.
---
Thomas Baden wrote:
> Hi there. My install was failing the regression tests
> due to a shared memory error.
>
> I'm running Solaris 5.8, YASSP, and I am using the Sun
>
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Thomas Baden wrote:
> Hi there. My insta
Hi there. My install was failing the regression tests
due to a shared memory error.
I'm running Solaris 5.8, YASSP, and I am using the Sun
Forte 7 compiler suite generating 64-bit code.
I did some digging around, and it turns out that the
IpcMemoryKey is a 64-bit number. The source code uses
ui
11 matches
Mail list logo
