not work with drbd,
but jfs seems to be quite good.
Regards,
Mario Weilguni
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
--
Greg Copeland, Owner
[EMAIL PROTECTED]
Copeland Computer Consulting
compounded by problems, I suspect it's again,
going to reflect poorly on the PostgreSQL community.
...just some ramblings
--
Greg Copeland, Owner
[EMAIL PROTECTED]
Copeland Computer Consulting
940.206.8004
---(end of broadcast)---
TIP 6: Have you
I tend to agree with this though I have nothing to back up it with. My
impression is that XFS does very well for large files. Accepting that
as fact?, my impression is that XFS historically does well for
database's. Again, I have nothing to back that up other than hear-say
and conjecture.
On Thu, 2002-09-26 at 09:52, Shridhar Daithankar wrote:
My friend argues for ext2 to eliminate journalling overhead but I favour
reiserfs personally having used it in pgbench with 10M rows on paltry 20GB IDE
disk for 25 tps..
We will be attempting raiserfs and/or XFS if required. I know
On Thu, 2002-09-26 at 11:41, Bruce Momjian wrote:
Shridhar Daithankar wrote:
I might have found the bottleneck, although by accident. Mysql was running out
of space while creating index. So my friend shut down mysql and tried to move
things by hand to create links. He noticed that even
On Thu, 2002-09-26 at 11:41, Bruce Momjian wrote:
Shridhar Daithankar wrote:
I might have found the bottleneck, although by accident. Mysql was running out
of space while creating index. So my friend shut down mysql and tried to move
things by hand to create links. He noticed that even
On Thu, 2002-09-26 at 16:03, Neil Conway wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Wow. That leaves no good Linux file system alternatives.
PostgreSQL just wants an ordinary file system that has reliable
recovery from a crash.
I'm not really familiar with the reasoning behind
On Sat, 2002-09-28 at 02:16, Shridhar Daithankar wrote:
On 28 Sep 2002 at 17:08, Justin Clift wrote:
Have moved the indexes to another drive, then created symlinks to them.
Ran a benchmark against the database, REINDEX'd the tables, VACUUM FULL
ANALYZE'd, prepared to re-run the benchmark
It was I that originally brought the topic up. I don't really remember
the exact details but I do seem to recall that the author thought it was
a horrid idea. Basically and poorly paraphrased the response was that
everyone should use select version() after they connect and if they
don't know to
Should an advisory be issued for production sites to not perform a
vacuum full with a notice that a bug fix will be coming shortly?
Greg
On Sat, 2002-09-28 at 13:45, Justin Clift wrote:
Bruce Momjian wrote:
I have seen no discussion on whether to go ahead with a 7.2.3 to add
several
Hey, excellent. Thanks!
Based on that, it appears that XFS is a pretty good FS to use. For me,
the real surprise was how well reiserfs performed.
Greg
On Thu, 2002-10-03 at 18:09, Mike Benoit wrote:
Some of you may be interested in this seemingly exhaustive benchmark
between ext2/3,
I wouldn't hold your breath for any form of threading. Since PostgreSQL
is process based, you might consider having a pool of sort processes
which address this but I doubt you'll get anywhere talking about threads
here.
Greg
On Fri, 2002-10-04 at 02:46, Hans-Jürgen Schönig wrote:
Did anybody
On Fri, 2002-10-04 at 09:40, Hans-Jürgen Schönig wrote:
I had a brief look at the code used for sorting. It is very well
documented so maybe it is worth thinking about a parallel algorithm.
When talking about threads: A pool of processes for sorting? Maybe this
could be useful but I
On Fri, 2002-10-04 at 10:37, Hans-Jürgen Schönig wrote:
My concern was that a process model might be a bit too slow for that but
if we had processes in memory this would be wonderful thing.
Yes, that's the point of having a pool. The idea is not only do you
avoid process creation and
On Fri, 2002-10-04 at 12:26, Bruce Momjian wrote:
Added to TODO:
* Allow sorting to use multiple work directories
Why wouldn't that fall under the table space effort???
Greg
signature.asc
Description: This is a digitally signed message part
On Fri, 2002-10-04 at 18:03, Neil Conway wrote:
Curtis Faith [EMAIL PROTECTED] writes:
It looks to me like BufferAlloc will simply result in a call to
BufferReplace smgrblindwrt write for md storage manager objects.
This means that a process will block while the write of dirty cache
obvious and is a common enhancement
yet seems to of been completely dismissed as people seem to be fixated
on I/O. Go figure.
Greg
On Fri, 2002-10-04 at 14:02, Bruce Momjian wrote:
Greg Copeland wrote:
-- Start of PGP signed section.
On Fri, 2002-10-04 at 12:26, Bruce Momjian wrote:
Added
implementation. If that's not the case, then parallel sorts
still seem like a rather obvious route to look into.
Greg
On Fri, 2002-10-04 at 14:15, Bruce Momjian wrote:
Greg Copeland wrote:
-- Start of PGP signed section.
I see. I just always assumed that it would be done as part of table
On Fri, 2002-10-04 at 14:31, Bruce Momjian wrote:
We use tape sorts, ala Knuth, meaning we sort in memory as much as
possible, but when there is more data than fits in memory, rather than
swapping, we write to temp files then merge the temp files (aka tapes).
Right, which is what I originally
On Thu, 2002-10-03 at 10:56, Shridhar Daithankar wrote:
Well, we were comparing ext3 v/s reiserfs. I don't remember the journalling
mode of ext3 but we did a 10 GB write test. Besides converting the RAID to RAID-
0 from RAID-5 might have something to do about it.
There was a discussion on
On Fri, 2002-10-04 at 15:07, Tom Lane wrote:
the sort comparison function can be anything, including user-defined
code that does database accesses or other interesting stuff. This
This is something that I'd not considered.
would mean that the sort auxiliary process would have to adopt the
On Sat, 2002-10-05 at 14:46, Curtis Faith wrote:
2) aio_write vs. normal write.
Since as you and others have pointed out aio_write and write are both
asynchronous, the issue becomes one of whether or not the copies to the
file system buffers happen synchronously or not.
Actually, I
On Sun, 2002-10-06 at 11:46, Tom Lane wrote:
I can't personally get excited about something that only helps if your
server is starved for RAM --- who runs servers that aren't fat on RAM
anymore? But give it a shot if you like. Perhaps your analysis is
pessimistic.
I do suspect my analysis
On Sun, 2002-10-06 at 18:07, Tom Lane wrote:
CPU loading goes from 80% idle at 1 client to 50% idle at 5 clients
to 10% idle at 10 or more.
So this does seem to be a nice win, and unless I hear objections
I will apply it ...
Wow Tom! That's wonderful! On the other hand, maybe people
On Mon, 2002-10-07 at 10:38, Antti Haapala wrote:
Browsed web and came across this piece of text regarding a Linux-KAIO
patch by Silicon Graphics...
Ya, I have read this before. The problem here is that I'm not aware of
which AIO implementation on Linux is the forerunner nor do I have any
On Mon, 2002-10-07 at 16:06, Curtis Faith wrote:
Well, too bad. If you haven't gotten your commit record down to disk,
then *you have not committed*. This is not negotiable. (If you think
it is, then turn off fsync and quit worrying ;-))
At this point, I think we've come full circle.
On Mon, 2002-10-07 at 15:28, Bruce Momjian wrote:
This is the trickle syncer. It prevents bursts of disk activity every
30 seconds. It is for non-fsync writes, of course, and I assume if the
kernel buffers get low, it starts to flush faster.
Doesn't this also increase the likelihood that
Clift wrote:
Greg Copeland wrote:
snip
If so, I assume it would become a configure option (--with-aio)?
Or maybe a GUC use_aio ?
:-)
Regards and best wishes,
Justin Clift
Regards,
Greg
On Tue, 2002-10-08 at 04:15, Zeugswetter Andreas SB SD wrote:
Can the magic be, that kaio directly writes from user space memory to the
disk ? Since in your case all transactions A-E want the same buffer written,
the memory (not it's content) will also be the same. This would automatically
Bruce,
Is there remarks along these lines in the performance turning section of
the docs? Based on what's coming out of this it would seem that
stressing the importance of leaving a notable (rule of thumb here?)
amount for general OS/kernel needs is pretty important.
Greg
On Tue, 2002-10-08
Can we please hold off until bison 1.50 becomes a defacto? It will be a
matter of weeks before distros offer this as an upgrade package let
alone months before distros offer this as a standard. Seems like these
changes are ideal for a release after next (7.5/7.6) as enough time will
of gone by
Oh, that's right. I had forgotten that it wasn't for general PostgreSQL
use. Since it's a ecpg deal only, I guess I remove my objection.
Greg
On Thu, 2002-10-10 at 09:18, Tom Lane wrote:
Greg Copeland [EMAIL PROTECTED] writes:
Can we please hold off until bison 1.50 becomes a defacto
On Fri, 2002-10-11 at 08:20, Antti Haapala wrote:
Quoted from one page
Because we couldn't get vacuum() to work reliable with PostgreSQL 7.1.1,
I have little respect for the MySQL advocacy guys. They purposely
spread misinformation. They always compare their leading edge alpha
software
of that, I wasn't sure if something else was being
implied.
Greg
On Fri, 2002-10-11 at 08:40, Shridhar Daithankar wrote:
On 11 Oct 2002 at 8:30, Greg Copeland wrote:
I'd be curious to hear in a little more detail what constitutes not
good for postgres on a mosix cluster.
On Fri, 2002-10-11 at 06
That a good idea. That way, if your database slows during specific
windows in time, you can vacuum larger sizes, etc. Seemingly would help
you better manage your vacuuming against system loading.
Greg
On Tue, 2002-10-15 at 19:22, Gavin Sherry wrote:
Hi all,
I'm thinking that there is an
On Wed, 2002-10-16 at 01:27, Shridhar Daithankar wrote:
Well, slow adoption rate is attributed to 'apache 1.3.x is good enough for us'
syndrome, as far as I can see from news. Once linux distros start shipping with
apache 2.x series *only*, the upgrade cycle will start rolling, I guess.
I
On Wed, 2002-10-16 at 02:29, Gavin Sherry wrote:
On 16 Oct 2002, Hannu Krosing wrote:
On Wed, 2002-10-16 at 05:22, Gavin Sherry wrote:
Hi all,
I'm thinking that there is an improvement to vacuum which could be made
for 7.4. VACUUM FULLing large, heavily updated tables is a pain.
But doesn't the solution I offer present a possible work around? The
table wouldn't need to be locked (I think) until the first dead tuple
were located. After that, you would only keep the locks until you've
scanned X% of the table and shrunk as needed. The result, I think,
results in
On Tue, 2002-10-22 at 22:28, Tom Lane wrote:
Greg Copeland [EMAIL PROTECTED] writes:
So again, I'm not really sure it they are meaningful at
this point.
psql might well have some internal leaks; the backend memory-context
design doesn't apply to it.
Okay. Thanks. I'll probably take
On Wed, 2002-10-23 at 08:48, Tom Lane wrote:
Greg Copeland [EMAIL PROTECTED] writes:
Okay. I've started looking at plpython to better understand it's memory
needs. I'm seeing a mix of mallocs and PLy_malloc. The PLy version is
basically malloc which also checks and reports on memory
If you were using them that frequently, couldn't you just keep a
persistent connection? If it's not used that often, wouldn't the
overhead of preparing the query following a new connection become noise?
Greg
On Wed, 2002-10-23 at 09:24, Hans-Jürgen Schönig wrote:
First of all PREPARE/EXECUTE
Could you use some form of connection proxy where the proxy is actually
keeping persistent connections but your application is making transient
connections to the proxy? I believe this would result in the desired
performance boost and behavior.
Now, the next obvious question...anyone know of any
periodically? If so, what tools are others using? I'm
currently using dmalloc for my curiosity.
[1] Not sure yet as I'm really wanting to find culumative leaks rather
than one shot allocations which are simply never freed prior to process
termination.
Regards,
Greg Copeland
On Tue, 2002-10-22 at 17:09, Tom Lane wrote:
Greg Copeland [EMAIL PROTECTED] writes:
I've started playing a little with Postgres to determine if there were
memory leaks running around. After some very brief checking, I'm
starting[1] to think that the answer is yes. Has anyone already gone
On Fri, 2002-10-25 at 00:52, Marc G. Fournier wrote:
Ya, I've thought that one through ... I think what I'm more looking at is
some way of 'limiting' persistent connections, where a server opens n
connections during a spike, which then sit idle indefinitely since it was
one fo those 'slashdot
I'd be curious to hear in a little more detail what constitutes not
good for postgres on a mosix cluster.
Greg
On Fri, 2002-10-11 at 06:15, Anuradha Ratnaweera wrote:
On Fri, Oct 11, 2002 at 04:29:53PM +0530, Shridhar Daithankar wrote:
Well, I don't think adding support for multiple
On Thu, 2002-10-17 at 22:20, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Let me add one more thing on this thread. This is one email in a long
list of Oh, gee, you aren't using that wizz-bang new
sync/thread/aio/raid/raw feature discussion where someone shows up and
wants to
to PostgreSQL, it
probably wouldn't be appropriate to followup on the mailing list.
Best Regards,
Greg Copeland
On Wed, 2002-10-30 at 02:19, Dave Page wrote:
-Original Message-
From: Greg Copeland [mailto:greg;copelandconsulting.net]
Sent: 30 October 2002 01:08
On Fri, 2002-11-29 at 07:19, Shridhar Daithankar wrote:
On 29 Nov 2002 at 7:59, Matthew T. O'Connor wrote:
On Thursday 28 November 2002 23:26, Shridhar Daithankar wrote:
On 28 Nov 2002 at 10:45, Tom Lane wrote:
This is almost certainly a bad idea. vacuum is not very
On Fri, 2002-11-29 at 06:59, Matthew T. O'Connor wrote:
On Thursday 28 November 2002 23:26, Shridhar Daithankar wrote:
On 28 Nov 2002 at 10:45, Tom Lane wrote:
Matthew T. O'Connor [EMAIL PROTECTED] writes:
interesting thought. I think this boils down to how many knobs do we
need to
for 7.4 of 7.5 time frame.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
. Again, this is
another area where I can imagine some tunable parameters.
Just to be on the safe side, I'm cc'ing Josh Drake at Command Prompt
(Mammoth) to see what they can offer up on it. Hope you guys don't
mind.
Greg
- Original Message -
From: Greg Copeland [EMAIL PROTECTED
). If GUC can fully satisfy, I certainly won't argue
against it.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
databases on n different drive sets for large production
databases.
That's right. I always forget about that. So, it seems, regardless of
the namespace effort, we shouldn't be limiting the number of concurrent
AVD's.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
the minor version number. If you did
neither but changed the source code at all, increment the third version
number, if we had one.
To be thoroughly amused, read the libtool source. Grep for 'version_type'.
--
Peter Eisentraut [EMAIL PROTECTED]
--
Greg Copeland [EMAIL
it, it is a
no-op. We have per-db and per-user settings, so GUC would allow such
control if you wish.
Ideally, it would be a tri-valued parameter, that is ON, OFF, or AUTO,
meaning it would determine if there was value in the compression and do
it only when it would help.
--
Greg Copeland [EMAIL
Perhaps compression should be added to the list of protocol changes.
This way, we can allow for per packet evaluation for compression.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
On Tue, 2002-12-10 at 21:50, Bruce Momjian wrote:
Tom Lane wrote:
Ian Barwick [EMAIL
thought you did it already?
I did only minor, which I knew was safe. Do folks realize this will
require recompile of applications by 7.3 users moving to 7.3.1? That
seems very drastic, and there have been very few problem reports about
the NOTIFY change.
--
Greg Copeland [EMAIL PROTECTED
over/backup)? A
simple dump/restore? Are there/is there any facilities in PorstgreSQL
for PITR archival which prevents PITR logs from be recycled (or perhaps,
simply archived off)? What about PITR streaming to networked and/or
removable media?
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer
..
HTH
Shridhar
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 2: you can get off all
of WAL's is
going to satisfactorily address the issue.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL
.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
on the head. ;)
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
On Tue, 2002-12-17 at 20:55, Neil Conway wrote:
On Tue, 2002-12-17 at 21:33, Greg Copeland wrote:
I do agree, GBorg needs MUCH higher visibility!
I'm just curious: why do we need GBorg at all? Does it offer anything
that SourceForge, or a similar service does not offer?
Especially given
PostgreSQL more frequently and build interest. It let's people know
that PostgreSQL is constantly being improved.
Mind share is a powerful thing and as any advertiser will tell you,
press releases is one of the best ways to get the word out.
Greg
--
Greg Copeland [EMAIL PROTECTED]
Copeland
a 7.3.1 tag in CVS. Do you guys do
something else for sub-releases? Case in point:
cvs [server aborted]: no such tag REL7_3_1_STABLE
It's still early here so I may be suffering from early morning brain
rot. ;)
Regards,
Greg
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer
.,
just as one would expect but nothing about 7.3 dot releases.
I'm still getting, cvs [server aborted]: no such tag REL7_3_1_STABLE.
Something overlooked here?
Regards,
Greg Copeland
On Mon, 2002-12-23 at 09:57, Bruce Momjian wrote:
Greg Copeland wrote:
On Sun, 2002-12-22 at 13:12
... no
configure: error: no acceptable C compiler found in $PATH
Thanks,
Al
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
--
Greg Copeland [EMAIL PROTECTED
doesn't
seem like a good fit for PostgreSQL.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
become
a HORRIBLE idea if any soft of scalability is desired.
Is it a FAQ? If not, it ought to be.
I agree. I think mlw's list of reasons should be added to a faq. It
terse yet says it all!
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end
shouldn't be using transient connections, no matter how
fast they are. This, in turn, brings you back to persistent connections
or connection pools/caches.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast
.
Exactly. Trying to speed up something that shouldn't be in the critical
path is exactly what I'm talking about.
I completely agree with you!
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 4: Don't
On Sat, 2003-01-04 at 04:27, Peter Eisentraut wrote:
Greg Copeland writes:
Just a reminder, there still doesn't appear to be a 7.3.1 tag.
There is a long tradition of systematically failing to tag releases in
this project. Don't expect it to improve.
Well, I thought I remembered from
backend.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
there was talk of adding a single user/admin only mode.
That is, where only the administrator can connect to the database.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
consider that to be a valid argument.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL
that a release should never happen unless source
has been tagged. Releases should ALWAYS be made from a checkout based
on tags.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 6: Have you searched our
a lot more meat before I'd
be convinced that threading is ready for PostgreSQL; from both a social
and technological perspective.
Regards,
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 2: you can get off
for IPv6
support but the kernel isn't compiled to support IPv6. If that is the
case, admittedly, you seem to have a point. If someone compiles in v6
support and their system doesn't have v6 support and it's been requested
via run-time config, it's should fail just like any other.
--
Greg Copeland
On Mon, 2003-01-06 at 15:43, Bruce Momjian wrote:
Greg Copeland wrote:
On Mon, 2003-01-06 at 15:29, Peter Eisentraut wrote:
(2) A socket type is explicitly enabled for the server to use, and if
creation fails, server startup fails. It seems that the current code
falls back to IPv4
On Mon, 2003-01-06 at 15:59, Bruce Momjian wrote:
Greg Copeland wrote:
It appears right at the top because creating the socket is the first
thing it does. A good question is once we have a way for the user to
control IPv4/6, what do we ship as a default? IPv4-only? Both
On Mon, 2003-01-06 at 16:17, Bruce Momjian wrote:
Greg Copeland wrote:
On Mon, 2003-01-06 at 15:59, Bruce Momjian wrote:
Greg Copeland wrote:
It appears right at the top because creating the socket is the first
thing it does. A good question is once we have a way for the user
10 years
ago) it wasn't all that Unix-like.
:-)
Regards and best wishes,
Justin Clift
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http
On Tue, 2003-01-07 at 02:00, Shridhar Daithankar wrote:
On 6 Jan 2003 at 6:48, Greg Copeland wrote:
1) Get I/O time used fuitfully
AIO may address this without the need for integrated threading.
Arguably, from the long thread that last appeared on the topic of AIO,
some hold that AIO
On Tue, 2003-01-07 at 12:21, Greg Stark wrote:
Greg Copeland [EMAIL PROTECTED] writes:
That's the power of using the process model that is currently in use. Should
it do something naughty, we bitch and complain politely, throw our hands in
the air and exit. We no longer have to worry
.
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
to
running out of memory. I cannot offhand think of a more brain-dead
behavior in any OS living or dead, but that's what it does.
Just FYI, I believe the 2.6.x series of kernels will rectify this
situation.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
,
it might be worth revisiting.
Robert Treat
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast
Views or C-functions, I think the idea is excellent. It's the concept
that I really like.
Greg
On Mon, 2003-01-13 at 15:00, Dave Page wrote:
-Original Message-
From: Greg Copeland [mailto:[EMAIL PROTECTED]]
Sent: 13 January 2003 20:56
To: Robert Treat
Cc: [EMAIL PROTECTED
, the author of it, and he seems to think it'd be pretty easy to
implement too.
Now, I'm not a C++ coder, and as short of time as anyone, so I was
wondering if there is anyone here who'd be interested in helping out here.
:-)
Regards and best wishes,
Justin Clift
--
Greg Copeland [EMAIL
the original thread's CPU. Most modern OS's do run each thread
within a process spread across n-CPUs. Those that don't are probably
attempting to modernize as we speak.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast
On Wed, 2003-01-22 at 23:40, Justin Clift wrote:
Justin Clift wrote:
Greg Copeland wrote:
Have you tried IBM's OSS visualization package yet? Sorry, I don't seem
to recall the name of the tool off the top of my head (Data Explorer??)
but it uses OpenGL (IIRC) and is said to be able
Should it be saying, Temporarily Unavailable?
Regards,
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command
got changed. I do remember that I chanced
some test code to ensure it tested the newly fixed data type.
Regards,
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
the distinction is? ...or
did I miss the humor boat? :(
Regards,
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
On Fri, 2003-01-31 at 13:04, Kurt Roeckx wrote:
On Thu, Jan 30, 2003 at 08:21:09PM -0600, Greg Copeland wrote:
It doesn't help the
confusion that many OS's try to confuse programmers by exposing a single
socket interface, etc. Simple fact remains, IPv6 is not IPv4.
It's a good things
come unglued if the largest
software audience in the world were completely ignored.
Simple fact is, your example really is pretty far off from supporting
any view. Bluntly stated, both are in that market because they want to
make money; they're even obligated to do so.
--
Greg Copeland [EMAIL
, more
fair comparison, as now we're talking about the same category of file
system.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
in (statically or dynamically)?
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL
directories (system,
windows, etc). My point being, just because you didn't find it in the
mysql directory, doesn't mean it wasn't installed system-wide.
Not saying it does or doesn't do this. Just offering something else
that may need to be looked at.
Regards,
--
Greg Copeland [EMAIL PROTECTED
1 - 100 of 213 matches
Mail list logo
