Peter Eisentraut <[EMAIL PROTECTED]> writes:
>> Now all you need is a free signal number. Unfortunately we're already
>> using both SIGUSR1 and SIGUSR2.
> Maybe you could dump the old meaning SIGQUIT (externally invoked error),
> move quickdie() to SIGQUIT, and you got SIGUSR1 free.
> (That woul
Adriaan Joubert writes:
> 1. Constants. The current behaviour just seems somewhat strange, and I
> have no idea where to fix it.
>
> test=# select B'1001';
> ?column?
> --
> X9
> (1 row)
Fixed. (Prints '1001'.)
> test=# select B'1001'::bit;
> ERROR: Cannot cast this expression to
> Tom Lane writes:
>
> > OK, we can probably assume that at least one of sigsuspend or sigpause
> > is available everywhere.
>
> #ifdef HAVE_POSIX_SIGNALS should tell you.
>
> > Now all you need is a free signal number. Unfortunately we're already
> > using both SIGUSR1 and SIGUSR2.
>
> Maybe
Tom Lane writes:
> OK, we can probably assume that at least one of sigsuspend or sigpause
> is available everywhere.
#ifdef HAVE_POSIX_SIGNALS should tell you.
> Now all you need is a free signal number. Unfortunately we're already
> using both SIGUSR1 and SIGUSR2.
Maybe you could dump the old
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > how about sigpause, and using SIGUSR1/SIGUSR2 to wake them up ?
>
> > The standard is sigsuspend:
>
> OK, we can probably assume that at least one of sigsuspend or sigpause
> is available everywhere. Now all you need is a free signal number.
Larry Rosenman writes:
> how about sigpause, and using SIGUSR1/SIGUSR2 to wake them up ?
Both of these signals are already used.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
Bruce Momjian <[EMAIL PROTECTED]> writes:
> how about sigpause, and using SIGUSR1/SIGUSR2 to wake them up ?
> The standard is sigsuspend:
OK, we can probably assume that at least one of sigsuspend or sigpause
is available everywhere. Now all you need is a free signal number.
Unfortunately
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> how about sigpause, and using SIGUSR1/SIGUSR2 to wake them up ?
>
> > Looks like a winner.
>
> sigpause() is a BSD-ism, and not part of any recognized standard
> according to my HP man pages. How portable do you think it is?
Good point. I get
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> how about sigpause, and using SIGUSR1/SIGUSR2 to wake them up ?
> Looks like a winner.
sigpause() is a BSD-ism, and not part of any recognized standard
according to my HP man pages. How portable do you think it is?
regards,
> * Tom Lane <[EMAIL PROTECTED]> [001117 23:21]:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > Other backend will see they are not the lowest
> > > WAIT_ON_FSYNC and will wait for their byte to be set to NOT_IN_COMMIT
> > > so they can then continue, knowing their data was synced.
> >
> > H
* Tom Lane <[EMAIL PROTECTED]> [001117 23:21]:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Other backend will see they are not the lowest
> > WAIT_ON_FSYNC and will wait for their byte to be set to NOT_IN_COMMIT
> > so they can then continue, knowing their data was synced.
>
> How will they w
Yes, I will make the change.
> Bruce Momjian writes:
>
> > The 7.1 code will the socket location configurable.
>
> Btw., are you still about to change it to the directory rather than the
> file? I'd suggest that you change the GUC parameter to
> "unix_socket_directory", to be consistent in nam
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > Other backend will see they are not the lowest
> > > WAIT_ON_FSYNC and will wait for their byte to be set to NOT_IN_COMMIT
> > > so they can then continue, knowing their data was synced.
> >
> > How will they wait? Without a semaphore involved,
13 matches
Mail list logo
