What about the use of priority inheritance to deal with the issue of
priority inversion (a standard methodology within the real-time world)?
Then we could have priorities, but still have low priority processes
bumped up if a high level one is waiting on them.
Regards,
Ed
On Wed, 20 Aug 2003, Tom
On Wed, 20 Aug 2003 14:44:28 -0700 David Olbersen <[EMAIL PROTECTED]> wrote:
> What is the point of bottom posting anymore? I thought it had to do with
> turn-around time so that you could re-read whatever it is you wrote a
> "long time ago". I highly doubt you would know, but is there an easy way
> it seems to me what would be more useful is an even
> lazier vacuum: something that could be told "clean up as cycles are
> available, but make sure you stay out of the way." Of course, that's
> easy to say glibly, and mighty hard to do, I expect.
You mean, like, "nice 19" or so ?
Karsten
--
G
I prefer NOT to have to scroll down to the bottom of an email anyway. I
think discussion list emails like ours need to be like your medical
records, the most important, recent stuff is at the top.
I'm not exactly sure what full quoting is.
David Olbersen wrote:
-Original Message-
From:
On Wed, 20 Aug 2003, Nigel J. Andrews wrote:
> On Wed, 20 Aug 2003, Dennis Gearon wrote:
>
> > holy S**T!!
>
> Particularly the 'Passed' number. Now I'm not subscribed to all of the lists
> but I am on -general, -hackers and a couple of others like -interfaces and yet
> I would say that the volume
> -Original Message-
> From: David W Noon [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 19, 2003 4:20 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [GENERAL] move to usenet?
>
> I agree that many messages are not formatted according to Usenet
> conventions, but I normally attribute that to
I think it would be nice, and I may write it eventually, to have a
function called:
COLLATION_VALUE( 'string', 'encoding' )
Which could be used like:
SELECT field_a, field_b
FROM table_a
GROUP BY COLLATION_VALUE( field_a )
ORDER BY COLLATION_VALUE( field_b );
or in other creative ways.
Greg St
Andrew Sullivan <[EMAIL PROTECTED]> writes:
>> I disagree. Triggering a vacuum on a db that is nearly saturating the
>> disk bandwidth has a significant impact.
> Vivek is right about this. If your system is already very busy, then
> a vacuum on a largish table is painful.
> I don't actually th
Tom Lane <[EMAIL PROTECTED]> writes:
> Greg Stark <[EMAIL PROTECTED]> writes:
> > My understanding is that the entire set of localization parameters needs to be
> > decided upon when the initdb is done and can never be changed later. Is that
> > right?
>
> No, not all of them are frozen. Unfortu
On Wed, 20 Aug 2003, Dennis Gearon wrote:
> holy S**T!!
Particularly the 'Passed' number. Now I'm not subscribed to all of the lists
but I am on -general, -hackers and a couple of others like -interfaces and yet
I would say that the volume of email I'm seeing from the lists is far lower
than norm
Well, the idea of mailing list is to exchange information and help
each other.
Obviously if few great things happen on some mailing list and others
don't come
to know it, defeats the purpose of having a mailing list.
I agree. This is one of my worries. If nothing happens on the French
list, it w
Greg Stark <[EMAIL PROTECTED]> writes:
> My understanding is that the entire set of localization parameters needs to be
> decided upon when the initdb is done and can never be changed later. Is that
> right?
No, not all of them are frozen. Unfortunately, the one you care about
(LC_COLLATE) is. T
Andrew Sullivan wrote:
On Wed, Aug 20, 2003 at 12:40:03PM -0400, Vivek Khera wrote:
> "BW" == Bruno Wolff, writes:
BW> Also, since at least 7.3, normal vacuums aren't normally going to
BW> affect the performance of your database server that much.
I disagree. Triggering a vacuum on a db that
On Tuesday 19 Aug 2003 09:06 in
<[EMAIL PROTECTED]>, Jules Alberts
([EMAIL PROTECTED]) wrote:
> This is not a troll and I certainly don't want to start a holy war but
> wouldn't it be a good idea to move the postgresql lists from the
> mailing list approach to usenet?
I don't know about anybody e
OK. I understand that you prefer a different approach. For my part, I
like to combine different approaches. I understand also that you
consider it impossible to put all the stuff into one database. I think
it is possible after all, but that is not the point here.
My request remains. I am lookin
On Tuesday 19 Aug 2003 15:43 in <[EMAIL PROTECTED]>, Chris M
([EMAIL PROTECTED]) wrote:
> I use outlook express to visit news.postgresql.org now.
> It works well.
Thank you for top-posting and full-quoting, just to prove my point. ... :-)
--
Regards,
Dave [RLU#314465]
I upgraded to 7.3.3 from 7.2 something. I guess the insert statment no longer
accepts a zero lenght string like ''
ERROR: pg_atoi: zero-length string
Is there a way to make this work so it will put Null in the place of it?
---(end of broadcast)
On Wed, 2003-08-20 at 15:57, The Hermit Hacker wrote:
> we haven't changed any of the list configs in months ...
Ok, thanks.
> On Wed, 20 Aug 2003, Ron Johnson wrote:
>
> > Hi,
> >
> > Up until a few days ago, when I did a "Reply to List" in my MUA
> > (Evolution 1.4.4), only [EMAIL PROTECTED] w
we haven't changed any of the list configs in months ...
On Wed, 20 Aug 2003, Ron Johnson wrote:
> Hi,
>
> Up until a few days ago, when I did a "Reply to List" in my MUA
> (Evolution 1.4.4), only [EMAIL PROTECTED] would show
> up in the "To:" list. Now, "Reply to List" acts like like "Reply
>
Hi,
Up until a few days ago, when I did a "Reply to List" in my MUA
(Evolution 1.4.4), only [EMAIL PROTECTED] would show
up in the "To:" list. Now, "Reply to List" acts like like "Reply
to All".
The reason I bring this up in [EMAIL PROTECTED] is that
"Reply to List" still acts properly wrt [EMAI
On Wed, Aug 20, 2003 at 12:40:03PM -0400, Vivek Khera wrote:
> > "BW" == Bruno Wolff, writes:
> BW> Also, since at least 7.3, normal vacuums aren't normally going to
> BW> affect the performance of your database server that much.
>
> I disagree. Triggering a vacuum on a db that is nearly sat
Jan Wieck <[EMAIL PROTECTED]> writes:
> Aah - there is the first bullet hole in my multi-ctid-index-idea. Now
> the question becomes how expensive these tests are (if a normal backend
> can do them at all within reason)?
It's not hugely expensive, IIRC, you just need to make some additional
chec
holy S**T!!
The Hermit Hacker wrote:
16:00 ...
neptune# awk '{print $7}' /var/log/amavisd | sort | uniq -c
285 BAD
1807 BANNED
12289 INFECTED
11731 Passed,
5 SA
1 turned
Here's a normal day:
neptune# cat /var/log/amavisd.o | grep "Aug 17" | awk '{print $7}' | sort
| uniq -c
332 BAD
13
On Wed, 2003-08-20 at 14:51, Tom Lane wrote:
> Bruno Wolff III <[EMAIL PROTECTED]> writes:
> > On Wed, Aug 20, 2003 at 13:44:59 -0500,
> > Ron Johnson <[EMAIL PROTECTED]> wrote:
> >> The GROUP BY does implicit sorting, so an ORDER BY on the exact same
> >> column(s) as the GROUP BY is redundant.
"P.J. \"Josh\" Rovero" <[EMAIL PROTECTED]> writes:
> 7.4b1 is significantly faster (i.e., the higher curve)
> over this range of clients and transactions.
Cool. I wonder though why the 7.4 curve is so much noisier.
regards, tom lane
---(end of bro
Tom Lane wrote:
Recall also that "committed deleted" does not mean "safe to remove".
There may still be live transactions that could see the tuple. The
"committed deleted" bit just exists to allow subsequent visitors to the
row to skip one of the more expensive steps in deciding whether they can
Stephan Szabo <[EMAIL PROTECTED]> writes:
> True, but the message being responded to was specifically "if the backend
> were to do the checking for external references upon updating/deleting a
> row".
It's clearly impossible for a backend to remove a row immediately upon
updating/deleting it, sinc
Bruno Wolff III <[EMAIL PROTECTED]> writes:
> On Wed, Aug 20, 2003 at 13:44:59 -0500,
> Ron Johnson <[EMAIL PROTECTED]> wrote:
>> The GROUP BY does implicit sorting, so an ORDER BY on the exact same
>> column(s) as the GROUP BY is redundant.
> That is an implementation detail, not a promise. Wit
My understanding is that the entire set of localization parameters needs to be
decided upon when the initdb is done and can never be changed later. Is that
right?
I have a multi-lingual web site, I want to be able to sort using collation
rules for en_US, en_CA, and fr_CA depending on the current
Vivek Khera <[EMAIL PROTECTED]> writes:
> "JW" == Jan Wieck <[EMAIL PROTECTED]> writes:
> JW> remove all the index entries pointing to these ctid's. Your idea is (so
> JW> far) lacking a place where to remember all the single removed rows and I
> JW> assume you're not planning to pay the cost of a
On Wed, 20 Aug 2003, Vivek Khera wrote:
> > "BW" == Bruno Wolff, writes:
>
> >> to see it incremental. This would result in pretty much near zero
> >> internal fragmentation, I think.
>
> BW> Why do you care about about the details of the implementation (rather than
> BW> the performance)?
On Wed, Aug 20, 2003 at 10:31:25AM -0400, Vivek Khera wrote:
> Seriously, how much slower can it be if the backend were to do the
> checking for external references upon updating/deleting a row? The
> cost would be distributed across time as opposed to concentrated at
> once within a vacuum proce
On Wed, Aug 20, 2003 at 10:31:25 -0400,
Vivek Khera <[EMAIL PROTECTED]> wrote:
>
> I care for the performance. And how are you so sure that it was
> faster the way it is now? Are you sure it was not done this way
> because of ease of implementation?
>
> Seriously, how much slower can it be if
> "BW" == Bruno Wolff, writes:
>> to see it incremental. This would result in pretty much near zero
>> internal fragmentation, I think.
BW> Why do you care about about the details of the implementation (rather than
BW> the performance)? If it were faster to do it that way, that's how it wou
See the attached file for details
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
On Wednesday 20 August 2003 19:01, Vasili G. Yanov wrote:
> >> I have trouble: when client-program broke connection to Postgre I see
> >> in logs:
> >>
> >> FATAL: This connection has been terminated by the administrator.
> >> LOG: shutting down
> >>
> >> and I must start Postgre again. Postg
On Wednesday 20 August 2003 18:51, Vasili G. Yanov wrote:
> I have trouble: when client-program broke connection to Postgre I see
> in logs:
>
> FATAL: This connection has been terminated by the administrator.
> LOG: shutting down
>
> and I must start Postgre again. Postgre starting as:
>
>
Please see the attached file for details.
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
I have trouble: when client-program broke connection to Postgre I see
in logs:
FATAL: This connection has been terminated by the administrator.
LOG: shutting down
and I must start Postgre again. Postgre starting as:
pg_ctl -D /usr/local/pgdata -o \"-S\" start
I have PostgreSQL 7.3.4 (b
On Tue, Aug 19, 2003 at 21:51:14 -0400,
Vivek Khera <[EMAIL PROTECTED]> wrote:
>
> I'm not promoting any change in the MVCC. What I'm saying is that it
> would be really cool if the backend process itself could recognize
> that a row is no longer referenced by any transactions upon
> terminatio
On Wed, 2003-08-20 at 08:11, The Hermit Hacker wrote:
> On Wed, 20 Aug 2003, Paul Thomas wrote:
>
> > There's a few come thru the list to me and I had a few more yesterday as
> > part of the daily spam. Like most people from the non-M$ world, this sort
> > of thing just passes me by :)
>
> I'm lo
On Wed, 2003-08-20 at 02:17, Christian Traber wrote:
> Hi,
>
> sometime ago I heard that there will be a native win32 version of
> postgresql 7.4.
> Is this true or will there only be a cygwin version like now?
>
The native win32 port has been pushed back from 7.4 into (hopefully)
7.5, but cygw
On Wed, 20 Aug 2003, Paul Thomas wrote:
> There's a few come thru the list to me and I had a few more yesterday as
> part of the daily spam. Like most people from the non-M$ world, this sort
> of thing just passes me by :)
I'm looking into how to add a 'taboo subject' filter onto the mj2 lists
th
On 20/08/2003 08:18 Nigel J. Andrews wrote:
Marc, I'd be interested in seeing the updated stats for this bought of
virus
transmission we're going through.
Yesterday you had almost 1 for 1 valid email. By then I think I was
getting
about 3-4 per valid email but since then it's sky rocketed and it
On Wed, 20 Aug 2003, Francois Suter wrote:
> > So far today:
> >
> > neptune# awk '{print $7}' /var/log/amavisd | sort | uniq -c
> > 137 BAD
> > 1732 BANNED
> > 4435 INFECTED
> > 6029 Passed,
>
> And still some make it through given some of the messages that are
> reaching the list today ("That m
So far today:
neptune# awk '{print $7}' /var/log/amavisd | sort | uniq -c
137 BAD
1732 BANNED
4435 INFECTED
6029 Passed,
And still some make it through given some of the messages that are
reaching the list today ("That movie" or "My details"). :-(
---
Francois
Home page: http://www.
On Wed, 20 Aug 2003, Jules Alberts wrote:
> Op 19 Aug 2003 (15:35), schreef The Hermit Hacker <[EMAIL PROTECTED]>:
> > On Tue, 19 Aug 2003, Jules Alberts wrote:
> >
> > > Hello everyone,
> > >
> > > This is not a troll and I certainly don't want to start a holy war but
> > > wouldn't it be a good
So far today:
neptune# awk '{print $7}' /var/log/amavisd | sort | uniq -c
137 BAD
1732 BANNED
4435 INFECTED
6029 Passed,
On Wed, 20 Aug 2003, Nigel J. Andrews wrote:
>
>
> Marc, I'd be interested in seeing the updated stats for this bought of virus
> transmission we're going through.
>
> Yest
Please see the attached file for details.
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Hi Philip,
See:
http://www.postgresql.org/docs/7.3/static/functions-subquery.html
..for starters.
Essentially, to perform the operation atomically I'd use:
begin;
update set = , ... where exists (select from where . = . (and).. etc..);
(actually i'd probably use a the from extension here
Op 19 Aug 2003 (15:35), schreef The Hermit Hacker <[EMAIL PROTECTED]>:
> On Tue, 19 Aug 2003, Jules Alberts wrote:
>
> > Hello everyone,
> >
> > This is not a troll and I certainly don't want to start a holy war but
> > wouldn't it be a good idea to move the postgresql lists from the
> > mailing l
Please see the attached file for details.
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Marc, I'd be interested in seeing the updated stats for this bought of virus
transmission we're going through.
Yesterday you had almost 1 for 1 valid email. By then I think I was getting
about 3-4 per valid email but since then it's sky rocketed and it looks more
like 30+ per 1 valid message.
I
53 matches
Mail list logo
