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
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
pattern doesn't match
it's page number accordingly, you know something is wrong. Storage cost
tends to be slightly and CPU overhead low.
I agree with you that a CRC is seems overkill for little return.
Regards,
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
. :-)
I do imagine for some people it will register high on their list.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail
rather see
people have to knowingly increase the limit rather than bump into system
upper limits and start scratching their heads trying to figure out what
the heck is going on.
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast
.
---
Greg Copeland wrote:
On Tue, 2003-02-11 at 18:27, Curt Sampson wrote:
On Wed, 11 Feb 2003, Greg Copeland wrote:
On Wed, 2003-02-05 at 18:53, Curt Sampson wrote:
[Re: everybody sharing a single key]
This issue doesn't change regardless
not provide for authentication and even more importantly,
verification of authentication. These concepts are key to creating a
secure environment.
Regards,
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
On Mon, 2003-02-10 at 21:57, [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED
between PHP and PostgreSQL. Does anyone know if we
can rule out some of the performance loss by pinning it to bad
middleware implementation for PostgreSQL?
Regards,
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast
,
however, I have no idea if MySQL's HEAP supports them. For all I know,
transactions are being silently ignored.
Regards,
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 2: you can get off all lists
On Wed, 2003-02-05 at 18:53, Curt Sampson wrote:
On Thu, 5 Feb 2003, Greg Copeland wrote:
Who will actually hold the key? Where will it be physically kept?
Good question but can usually be addressed.
It can be addressed, but how well? This is another big issue that I
. ;)
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 Tue, 2003-02-11 at 11:23, mlw wrote:
Greg Copeland wrote:
I'd personally rather have people stumble trying to get PostgreSQL
running, up front, rather than allowing the lowest common denominator
more easily run PostgreSQL only to be disappointed with it and move on.
After it's
relate to the web. I'm
thinking I'm not alone.
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
/mapped via pagefile. This is the preferred means of memory
mapped files unless you have a specific need which dictates otherwise.
Meaning, it allows for many supposed optimizations to be used by the OS
as it is suppose to bypass some of the filesystem overhead.
Regards,
--
Greg Copeland [EMAIL
On Tue, 2003-02-11 at 18:27, Curt Sampson wrote:
On Wed, 11 Feb 2003, Greg Copeland wrote:
On Wed, 2003-02-05 at 18:53, Curt Sampson wrote:
[Re: everybody sharing a single key]
This issue doesn't change regardless of the mechanism you pick. Anyone
that is signing a key must take
On Tue, 2003-02-04 at 18:27, Curt Sampson wrote:
On Tue, 2003-02-04 at 16:13, Kurt Roeckx wrote:
On Tue, Feb 04, 2003 at 02:04:01PM -0600, Greg Copeland wrote:
Even improperly used, digital signatures should never be worse than
simple checksums. Having said that, anyone
On Wed, 2003-02-05 at 00:22, Curt Sampson wrote:
On Wed, 4 Feb 2003, Greg Copeland wrote:
If three people are required to sign a package prior to release,
what happens when one of them is unavailable for signing (vacation,
hospital, etc). This is one of the reasons why having a single
,
I'm curious as to why you think adjusting the MTU may have an effect on
this. Lowering the MTU may actually increase fragmentation, lower
efficiency, and even exacerbate the situation.
Is this purely a diagnostic suggestion?
Regards,
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer
generated, it
should not leave his eyes until it has been signed.
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
are not, in of themselves, a security mechanism. I can't stress this
enough. There really isn't any comparison here. Please stop comparing
apples and oranges. No matter how hard you try, you can not make orange
juice from apples.
Regards,
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer
On Tue, 2003-02-04 at 16:13, Kurt Roeckx wrote:
On Tue, Feb 04, 2003 at 02:04:01PM -0600, Greg Copeland wrote:
Even improperly used, digital signatures should never be worse than
simple checksums. Having said that, anyone that is trusting checksums
as a form of authenticity validation
signed with a key which can
be readily validated from multiple independent sources.
Regards,
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Mon, 2003-02-03 at 13:55, Kurt Roeckx wrote:
On Mon, Feb 03, 2003 at 12:24:14PM -0600, Greg Copeland wrote:
On Sun, 2003-02-02 at 20:23, Marc G. Fournier wrote:
right, that is why we started to provide md5 checksums ...
md5 checksums only validate that the intended package
across America and the around the world, surely it's
good enough to help propagate key information for signing packages.
Regards,
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 4: Don't 'kill -9
. Of course, nothing beats meeting in person having
valid ID and fingerprints in hand. ;)
Regards,
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http
signed and
can reasonably verify that the signing key is safe and/or can be
verified, confidence should be high in the signed package.
I certainly have no problem with people signing my key nor with signing
others as long as we can verify/authenticate each others keys prior.
Regards,
--
Greg
On Sat, 2003-02-01 at 00:34, Adam Haberlach wrote:
On Sat, Feb 01, 2003 at 12:27:31AM -0600, Greg Copeland wrote:
On Fri, 2003-01-31 at 14:36, Dave Page wrote:
I intend to run the tests on a Dual PIII 1GHz box, with 1Gb of Non-ECC
RAM and a 20Gb (iirc) IDE disk. I will run on Windows
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
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
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
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
of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
--
Greg Copeland [EMAIL PROTECTED]
Copeland Computer Consulting
---(end of broadcast)---
TIP 6: Have you searched our
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
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
, 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
,
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
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
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
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
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
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
... 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
.,
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
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
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
.
--
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
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
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
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
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
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-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
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 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
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
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 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
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
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 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
1 - 100 of 213 matches
Mail list logo