Oliver Jowett <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> However, I would still like to know why 7.4 didn't show the same
>> misbehavior, when it isn't using this flag.
> It looks like the 7.4 code never unblocks signals in the collector
> process, so that process never gets stopped by SIGT
Tom Lane wrote:
Oliver Jowett <[EMAIL PROTECTED]> writes:
I think pqsignal should be passing SA_NOCLDSTOP in sa_flags,
With that patch applied, the problem is indeed gone on my system.
However, I would still like to know why 7.4 didn't show the same
misbehavior, when it isn't using this flag.
It l
Steve Bergman wrote:
Anyone have an SRPM of spec file for the beta?
(moved to HACKERS)
I just created and posted a source RPM for 8.0.0beta1. As I'm not the
usual packager, and a pure hack when it comes to building my own RPMs,
it would be a Good Thing(tm) if someone else could vet this package;
Oliver Jowett <[EMAIL PROTECTED]> writes:
> I think pqsignal should be passing SA_NOCLDSTOP in sa_flags,
With that patch applied, the problem is indeed gone on my system.
However, I would still like to know why 7.4 didn't show the same
misbehavior, when it isn't using this flag.
Oliver Jowett <[EMAIL PROTECTED]> writes:
> I think pqsignal should be passing SA_NOCLDSTOP in sa_flags,
Hmm, that does look like a good idea ... but it does not explain why 7.4
doesn't have the same problem.
regards, tom lane
---(end of broadcast)
Tom Lane wrote:
Jan Wieck <[EMAIL PROTECTED]> writes:
In that context, is SIGTSTP similar to SIGSTOP in that it cannot be
caught or ignored?
Possibly. I've reproduced the problem here on an RHL 8 system
(2.4.18 kernel) and I think it's a kernel bug. Points:
[...]
I can reproduce this on a 2.6.7
On Sat, 14 Aug 2004, Bruce Momjian wrote:
> Christopher Kings-Lynne wrote:
> > > Yeah, those are all bug fixes and okay for post-beta I think. But which
> > > two tablespace failures are you thinking of exactly? The last couple
> > > weeks have been a bit of a blur for me...
> >
> > http://group
Jan Wieck <[EMAIL PROTECTED]> writes:
> In that context, is SIGTSTP similar to SIGSTOP in that it cannot be
> caught or ignored?
Possibly. I've reproduced the problem here on an RHL 8 system
(2.4.18 kernel) and I think it's a kernel bug. Points:
1. AFAICS, the only case where the stats buffer
On 8/14/2004 11:38 PM, Tom Lane wrote:
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
I see stats collector processes die in current when I suspend
postmaster then put it in background from a terminal:
Is this normal?
Doesn't 7.4 behave the same?
It looks to me like 7.4 and current have the same signal
Ooh, how about the 'there is no security checking on the cluster on
index command' bug?
Chris
Christopher Kings-Lynne wrote:
Hi,
Should be backport the 'fix acls on owner to' on tables to 7.4? The
other acl objects did not have owner to commands in 7.4 IIRC, but the
alter table is definitely b
> Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> > I see stats collector processes die in current when I suspend
> > postmaster then put it in background from a terminal:
>
> > Is this normal?
>
> Doesn't 7.4 behave the same?
No.
> It looks to me like 7.4 and current have the same signal handling.
Bruce Momjian <[EMAIL PROTECTED]> writes:
> However, I don't see any CVS commit that fixed this? What am I missing?
The failure case is where the template database has a conflicting
table. You didn't show us where you created that table, but it
evidently was not in template1.
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> I see stats collector processes die in current when I suspend
> postmaster then put it in background from a terminal:
> Is this normal?
Doesn't 7.4 behave the same?
It looks to me like 7.4 and current have the same signal handling.
I'm not sure why a ts
Tom Lane wrote:
> > http://groups.google.com.au/groups?q=tablespaces+group:comp.databases.postgresql.hackers&hl=en&lr=&ie=UTF-8&group=comp.databases.postgresql.hackers&scoring=d&selm=4107211C.2050508%40familyhealth.com.au&rnum=5
>
> I think the problem here is that we don't have a syntax for sayin
Christopher Kings-Lynne wrote:
> > Yeah, those are all bug fixes and okay for post-beta I think. But which
> > two tablespace failures are you thinking of exactly? The last couple
> > weeks have been a bit of a blur for me...
>
> http://groups.google.com.au/groups?q=tablespaces+group:comp.databa
I see stats collector processes die in current when I suspend
postmaster then put it in background from a terminal:
$ ps x
:
:
21638 pts/1S 0:00 /bin/bash -i
30525 pts/1S 0:00 postmaster
30527 pts/1S 0:00 postgres: writer process
30528 pts/1S 0:00 postgres: s
Added to open items:
* fix recovery of DROP TABLESPACE after checkpoint
---
Tom Lane wrote:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> > Maybe we could avoid removing it until the next checkpoint? Or
I am catching up on my email. I am OK reading the email, but am
back-logged in dealing with email that needs my attention.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> The patch is not platform-specific. It simply makes psql accept the same
> line endings on COPY FROM that the backend will accept - in effect it
> makes it line-end agnostic - this is a Good Thing (tm).
Strictly speaking it's not there yet --- psql st
On Sat, 2004-08-14 at 01:11, Tom Lane wrote:
> Eric Kerin <[EMAIL PROTECTED]> writes:
> > The issues I've seen are:
> > 1. Knowing when the master has finished the file transfer transfer to
> > the backup.
>
> The "standard" solution to this is you write to a temporary file name
> (generated off y
Andrew Dunstan wrote:
>
>
> Bruce Momjian wrote:
>
> >One issue is that pre-8.0, psql files were opened in Win32 text mode, so
> >we wouldn't have seen this bug on Win32, but we would on Linux.
> >Because we open them on Win32 now in binary mode so we see control-Z it
> >will show up on Win32
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Josh Berkus wrote:
>> b) Procedures are not automatically transactional; that is,
>> transactions within procedures must/can be explicit. Among other
>> things, this would allow procedures to run maintainence tasks.
> I certainly want all my maintena
Bruce Momjian wrote:
One issue is that pre-8.0, psql files were opened in Win32 text mode, so
we wouldn't have seen this bug on Win32, but we would on Linux.
Because we open them on Win32 now in binary mode so we see control-Z it
will show up on Win32 too.
true, *BUT*
The patch is not platfo
Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
>
> >"Andrew Dunstan" <[EMAIL PROTECTED]> writes:
> >
> >
> >>No, I think 7.4 should do. 7.3 users will still have the dos2unix workaround
> >>available. Are you going to do the 7.4 patch, or do you need me to? I
> >>normally only keep a HEAD tree ch
Peter Eisentraut wrote:
Josh Berkus wrote:
Dennis has pointed out that mixing the call-with-named-parameter
interface with call-by-order-of-parameters one would cause
confusion, and I think it would be OK to disallow this type mixing,
so
As we've discussed on IRC, this should be the diff
Josh Berkus wrote:
> > Dennis has pointed out that mixing the call-with-named-parameter
> > interface with call-by-order-of-parameters one would cause
> > confusion, and I think it would be OK to disallow this type mixing,
> > so
>
> As we've discussed on IRC, this should be the difference between
In the last exciting episode, [EMAIL PROTECTED] (Bruce Momjian) wrote:
> Tom Lane wrote:
>> Christopher Browne <[EMAIL PROTECTED]> writes:
>> > Oops! [EMAIL PROTECTED] (Reinoud van Leeuwen) was seen spray-painting on a wall:
>> >> Why? I understood that using BitKeeper for free for Open Source proj
David,
> Dennis has pointed out that mixing the call-with-named-parameter
> interface with call-by-order-of-parameters one would cause confusion,
> and I think it would be OK to disallow this type mixing, so
As we've discussed on IRC, this should be the difference between a FUNCTION
and a PROCED
HI,
Compiling beta1 on Unixware 714 is OK, regression test are ok (with the
mp1 patch applied)
However make check-install fails if default_with_oids=false in
postgresql.conf (witch is normal regarding regression tests) but they
might be changed in a other version when you guys change this to fals
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> Should be backport the 'fix acls on owner to' on tables to 7.4?
I'm inclined not to, as (a) it's a moderately complex change that hasn't
yet been tested to my satisfaction, and (b) AFAIR we've not had any
complaints from the field about it, eve
Tom Lane wrote:
David Fetter <[EMAIL PROTECTED]> writes:
CREATE OR REPLACE FUNCTION foo_func(name TEXT, val INTEGER) AS ...
SELECT foo_func(val AS 23, name AS 'Name goes here');
I don't think that syntax will work. You could possibly do it the other
way round:
SELECT foo_func(23 AS val, 'Name go
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
>> Right, also an area that needs thought. Some other people opined that
>> they want the switchover to occur only on manual command. I'd go with
>> that too if you have anything close to 24x7 availability of admins.
>> If you *mu
Gaetano Mendola wrote:
BTW other projects are carrying also a build version in order to
distinguish
between two 8.0beta1 versions.
Except that we don't officially publish builds, only source sets.
Actually, this might be a reson to chenge to a different SCC system -
svn at least has a unique t
Oliver Jowett wrote:
Gaetano Mendola wrote:
Oliver Jowett wrote:
> David Fetter wrote:
>
>> Dennis has pointed out that mixing the call-with-named-parameter
>> interface with call-by-order-of-parameters one would cause
confusion,
>
> Python's equivalent sy
Andrew Dunstan wrote:
Gaetano Mendola wrote:
Bruce Momjian wrote:
>
> Yes, the fix will be in beta2 or the next pginstaller release.
Do you mean that the next pginstaller release will carry a 8.0beta1
with different behaviour that actual 8.0beta1 ?
I hope I mistake you.
What are you talking about
Oliver Jowett wrote:
> Gaetano Mendola wrote:
>
>> Oliver Jowett wrote:
>>
>>> Gaetano Mendola wrote:
>>>
Oliver Jowett wrote:
> David Fetter wrote:
>
>> Dennis has pointed out that mixing the call-with-named-parameter
>> interface with call-by-order-of-parameters one woul
Harald Fuchs wrote:
In article <[EMAIL PROTECTED]>,
Oliver Jowett <[EMAIL PROTECTED]> writes:
I think you just made my point for me. C++ allows default parameters
and resolves the ambiguity by disallowing ambiguous calls when they
happen.
I'm not sure why C++ doesn't disallow it at declaration t
Gaetano Mendola wrote:
Oliver Jowett wrote:
> David Fetter wrote:
>
>> Dennis has pointed out that mixing the call-with-named-parameter
>> interface with call-by-order-of-parameters one would cause
confusion,
>
> Python's equivalent syntax allows you to mi
Gaetano Mendola wrote:
Bruce Momjian wrote:
>
> Yes, the fix will be in beta2 or the next pginstaller release.
Do you mean that the next pginstaller release will carry a 8.0beta1
with different behaviour that actual 8.0beta1 ?
I hope I mistake you.
What are you talking about? The installer projec
In article <[EMAIL PROTECTED]>,
Oliver Jowett <[EMAIL PROTECTED]> writes:
> I think you just made my point for me. C++ allows default parameters
> and resolves the ambiguity by disallowing ambiguous calls when they
> happen.
> I'm not sure why C++ doesn't disallow it at declaration time off the
Tom Lane wrote:
"Andrew Dunstan" <[EMAIL PROTECTED]> writes:
No, I think 7.4 should do. 7.3 users will still have the dos2unix workaround
available. Are you going to do the 7.4 patch, or do you need me to? I
normally only keep a HEAD tree checked out. A quick look at the cvsweb diffs
suggests t
> Tom Lane
> Eric Kerin <[EMAIL PROTECTED]> writes:
> > The issues I've seen are:
> > 1. Knowing when the master has finished the file transfer transfer to
> > the backup.
>
> The "standard" solution to this is you write to a temporary file name
> (generated off your process PID, or some other conv
Gaetano Mendola wrote:
Oliver Jowett wrote:
Gaetano Mendola wrote:
Oliver Jowett wrote:
David Fetter wrote:
Dennis has pointed out that mixing the call-with-named-parameter
interface with call-by-order-of-parameters one would cause confusion,
Python's equivalent syntax allows you to mix the two fo
Gaetano Mendola wrote:
C++ manages to solve this problem, although I can't remember the exact
mechanics (and C++ is usually not a good example to follow anyway ;)
Your're wrong:
try to compile this: [...]
a.cpp:6: error: call of overloaded `foo(int, double)' is ambiguous
a.cpp:1: error: candidate
David Fetter wrote:
> I'd like to be able to create functions with named parameters that
> could be called with the names in any order. For example,
>
> CREATE OR REPLACE FUNCTION foo_func(name TEXT, val INTEGER) AS ...
>
> SELECT foo_func(val AS 23, name AS 'Name goes here');
When that was broug
Hi,
Should be backport the 'fix acls on owner to' on tables to 7.4? The
other acl objects did not have owner to commands in 7.4 IIRC, but the
alter table is definitely broken.
Chris
---(end of broadcast)---
TIP 5: Have you checked our extensive FA
Bruce Momjian wrote:
> Pierre-Frédéric Caillaud wrote:
> > Is there also a possibility to tell Postgres : "I don't care if I
> > lose 30 seconds of transactions on this table if the power goes
> > out, I just want to be sure it's still ACID et al. compliant but
> > you can fsync less often and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I seen that Eric Kerin did the work suggested by Tom about
how to use the PITR in order to have an hot spare postgres,
writing a C program.
I did the same writing 2 shell scripts, one of them perform
the restore the other one deliver the partial
> Tom Lane wrote
> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> > It would be my intention (in 8.1) to make those available via
> switches e.g.
> > NOT LOGGED options on CREATE INDEX and COPY, to allow users to take
> > advantage of the no logging optimization without turning off PITR system
>
Eric Kerin wrote:
On Wed, 2004-08-11 at 16:43, Tom Lane wrote:
Gaetano Mendola <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
It should work; dunno if anyone has tried it yet.
I was thinking about it but I soon realized that actually is
impossible to do, postgres replay the log only if during the
sta
Peter Eisentraut wrote:
> Why is the encoding WIN 1250 only for the client side? It seems that
> with the new Windows port, folks will be interested in using it on
> the server side.
Last call or I will move WIN 1250 to the server side encoding list. The
bugs are already coming in.
--
Peter Ei
Oliver Jowett wrote:
Tom Lane wrote:
On a related note, it would also be nice to have default
parameters and some way to say to use them.
That is fundamentally not ever going to happen, because it blows
overloaded-function resolution out of the water: there is no way to
choose whether "foo(42, 2.5
Oliver Jowett wrote:
Gaetano Mendola wrote:
Oliver Jowett wrote:
David Fetter wrote:
Dennis has pointed out that mixing the call-with-named-parameter
interface with call-by-order-of-parameters one would cause confusion,
Python's equivalent syntax allows you to mix the two forms so long as
all the
Bruce Momjian wrote:
> Andrew Dunstan wrote:
>
>>
>>[EMAIL PROTECTED] wrote:
>>
>>
>>>I notice that PITR doesn't function correctly on Windows. Has that been
>>>reported elsewhere?
>>>
>>>The archive_command parameter %p resolves to a full path containing slashes
>>>rather than backslashes. This is
54 matches
Mail list logo
