Mike Mascari <[EMAIL PROTECTED]> writes:
> However, I did find this
> explanation as to why on the Microsoft Knowledge Base:
> http://support.microsoft.com/support/kb/articles/Q237/9/92.ASP
Interesting. Apparently, at this point our "Microsoft-compatible"
hack is arguably *failing* to be Micros
On Thu, Jun 14, 2001 at 05:10:58PM -0400, Tom Lane wrote:
> Doug McNaught <[EMAIL PROTECTED]> writes:
> > Tom Lane <[EMAIL PROTECTED]> writes:
> >> Hm. That's one way, but is it really any cleaner than our existing
> >> technique? Since you still need to assume you can do a system call
> >> in a
Alex Pilosov <[EMAIL PROTECTED]> writes:
> Indexpath generated for such an expression is this:
> (a > network(b)) and (a <= set_masklen(broadcast(b, 32)))
What happens to that set_masklen thing for IPv6?
If the network.c code were exporting a function that made this value,
I'd not worry; but I d
Per previous discussions, I have modified initdb to revoke public read
access on pg_statistic (you can still read it if you're superuser,
of course) and instead added a view pg_stats, which will show the
statistics rows only for tables that current_user has read access to.
This uses the has_table_
On Thu, Jun 14, 2001 at 04:27:14PM -0400, Tom Lane wrote:
> [EMAIL PROTECTED] (Nathan Myers) writes:
> > It could open a pipe, and write(2) a byte to it in the signal handler,
> > and then have select(2) watch that pipe. (SIGHUP could use the same pipe.)
> > Of course this is still a system call
Doug McNaught <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> writes:
>> Hm. That's one way, but is it really any cleaner than our existing
>> technique? Since you still need to assume you can do a system call
>> in a signal handler, it doesn't seem like a real gain in
>> bulletproofn
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> Also note that we could easily fix things so that the max-number-of-
>> backends limit is not checked until we have passed the authentication
>> procedure. A PM child that's still busy authenticating doesn't have
>> to count.
> H
[EMAIL PROTECTED] (Nathan Myers) writes:
> It could open a pipe, and write(2) a byte to it in the signal handler,
> and then have select(2) watch that pipe. (SIGHUP could use the same pipe.)
> Of course this is still a system call in a signal handler, but it can't
> (modulo coding bugs) fail.
H
On Thu, Jun 14, 2001 at 02:18:40PM -0400, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > I notice that the signal handlers in postmaster.c do quite a lot of work,
> > much more than what they teach you in school they should do.
>
> Yes, they're pretty ugly. However, we have n
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I notice that the signal handlers in postmaster.c do quite a lot of work,
> much more than what they teach you in school they should do.
Yes, they're pretty ugly. However, we have not recently heard any
complaints suggesting problems with it. Since
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> If we did this the straightforward way (exchange authentication packets
> after fork()) then rogue clients could connect, start a backend, twiddle
> thumbs, never finish the authentication exchange, meanwhile having filled
> up the limit on the number
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> ... the whole business of temprels having different physical and
>> logical relnames will go away anyhow. Temp rels will become plain rels
>> that live in a temp schema.
> I don't think this is the right solution. You should be
Hannu Krosing <[EMAIL PROTECTED]> writes:
> I could send you tails of postgres logfiles that are rotated on
> detecting
> the INSERT/UPDATE wait condition that does not go away in 10 sec.
> How long logfiles (time) would be enough ?
Do the logs show the queries being executed? The queries form
> mlw wrote:
>> After we run the
>> scripts, it looks like the database is corrupt.
It's impossible to say anything useful with such an undescriptive
description of the problem.
Hannu Krosing <[EMAIL PROTECTED]> writes:
> There certainly are bugs in 7.0.3 - I can describe at least two:
I would
Hello Robert (Bob?),
Thank you for your answer. I will surely make a wide use the COALESCE
function in my scripts.
I also noticed the same behaviour in PL/pgSQL:
CREATE FUNCTION "xx" (text, text)
RETURNS text
AS 'BEGIN
RETURN $1 || ' ' || $2;
END;
'
LANGUAGE 'plpgsql'
Correct me i
15 matches
Mail list logo
