Christopher Kings-Lynne wrote:
Are my mails getting through? Did anyone see my mail about the GIN docs?
I got it.
Joshua D. Drake
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
currently have the customer running hardware checks to verify validity
of the hardware but...
Any thoughts?
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
Dave Cramer and I have dealt with a company today running 8.1.4 on
Windows 2003. The application is a web app that runs via JDBC/Hibernate.
The application will function perfectly for about 2/3 weeks and then we
will receive a:
server
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
Tom Lane wrote:
BTW, are you sure this is coming from JDBC? I see the exact same
message text in libpq:
libpq_gettext(server sent data (\D\ message) without prior row description (\T\
message)\n));
Maybe the JDBC driver uses
is
because PostgreSQL no longer responds. The system itself is fine.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
My bet is something depending on GetTickCount to measure elapsed time
(and no, it's not used in the core Postgres code, but you've got plenty
of other possible culprits in that stack).
This doesn't quite make sense. The only reason we
Alvaro Herrera wrote:
Dave Cramer wrote:
On 31-Aug-06, at 6:01 PM, Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
Tom Lane wrote:
BTW, are you sure this is coming from JDBC? I see the exact same
message text in libpq:
libpq_gettext(server sent data (\D\ message) without prior
. The less cats to herd the better :)
Joshua D. Drake
Cheers,
Steve
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
--
=== The PostgreSQL Company: Command Prompt, Inc
that is shipped before
it is done?
Outside of feature freeze, we really haven't had AFAICS a solid
release schedule. Is it going to be push Beta for a month? Does that
push us till the end of the year?
I don't know which is the better solution, but you asked for comments :)
Sincerely,
Joshua D
* perspective.
What makes the analyst (and I know this isn't the communities problem)
say, Holy crap batman, we need to be talking to more people about this
database. I think those would be Updateable views, Bitmap Indexes and
the SQL2003-standard statistical aggregates.
Sincerely,
Joshua D
!
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
---(end
Alvaro Herrera wrote:
Joshua D. Drake wrote:
It does not mean all those features are useful, they definitely are. I
am just trying to look at it from at:
WHIZ* BANG* POW* perspective.
Holy crap, Batman! This database can do
INSERT INTO foo VALUES (1,1, 'so long'), (42, 2, 'and thanks
and community sections.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com
it. It is a URL. Why do people care where it is?
I would think that it would be easier to find :)
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions
guess that you are correct :).
I find also that this method allows someone like me, who can read C and
understand good parts of it to get the gist of what is going on without
trying to grok the whole thing. Large patches make it very difficult.
Sincerely,
Joshua D. Drake
things.
Greg, how about you and I (I am talking with Dunstan on this as well)
set up Bugzilla and just doing an small group audit of how it could (or
couldn't) work and report back?
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support
was the wrong
place to put it. Not that I am slamming your efforts, I think it was
really good that you did the docs :). They are just in the wrong place.
Sincerely,
Joshua D. Drake
regards,
Lukas
---(end of broadcast)---
TIP 9: In versions below 8.0
Peter Eisentraut wrote:
Since the buildfarm is such an integral part of the development process
now, could we get it an enhanced URL like buildfarm.postgresql.org?
All we have to do is point the DNS :), I can make the apache changes.
Sincerely,
Joshua D. Drake
. :). It wasn't supposed to be an open wiki
like that.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http
are after :)
Sincerely,
Joshua D. Drake
---
Joshua D. Drake wrote:
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
Can we get:
Well this should be fun.
Multiple table indexes (for uniqueness across partitions
Bruce Momjian wrote:
Joshua D. Drake wrote:
Bruce Momjian wrote:
Added to TODO:
* Simplify ability to create partitioned tables
This would allow creation of partitioned tables without requiring
creation of rules for INSERT/UPDATE/DELETE, and constraints
email).
Joshua D. Drake
cheers
andrew
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency
Christopher Browne wrote:
Oops! [EMAIL PROTECTED] (Jim C. Nasby) was seen spray-painting on a wall:
On Thu, Aug 31, 2006 at 10:33:36AM -0400, Chris Browne wrote:
What's up there? It has been down all week.
We're trying to get the Slony-I 1.2 release out, so we can then
migrate over to
some time.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com
Peter Eisentraut wrote:
Joshua D. Drake wrote:
http://pgbugs.commandprompt.com (still need to configure email).
Thank you for that.
I think an issue tracking system for patches and such may need to be
distinct from a bug-tracking system such as bugzilla, but let's get one
thing after
to release.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com
Oleg Bartunov wrote:
On Sun, 3 Sep 2006, Joshua D. Drake wrote:
I can see various things that we might consider doing:
1. Just flip the names of the two operators added by the GIN patch.
2. #1 plus flip the names of the various contrib operators that are
out of sync (Michael Fuhr points
don't think anyone would expect that (at least I wouldn't). Heck, even
I wouldn't use a web forum.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive
The *big* steps are moving email and CVS.
*big* but quite easy :) As long as we have an mbox file from the slony
lists, we can import easily into pgfoundry.
CVS is just an rsync ;)
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support
and it would correct associate as a bug.
Joshua D. Drake
cheers
andrew
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
of volunteers to help maintain it.
I need someone to help look at this email interface in the contrib to
see how it can be modified to allow email interaction. Based on the
documentation of its current abilities, it actually looks like it won't
take too much.
Takers?
Sincerely,
Joshua D
will answer the call?
I concur, more then one person has complained on this thread and others
about wanting these tools. It is time that those people step up.
Sincerely,
Joshua D. Drake
regards, tom lane
--
=== The PostgreSQL Company: Command Prompt, Inc
about ACK-vs-NAK requirements for something to go
in.
How about *requiring* test cases that prove the patch?
Sincerely,
Joshua D. Drake
regards, tom lane
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Gavin Sherry wrote:
On Mon, 4 Sep 2006, Joshua D. Drake wrote:
I don't have a concrete proposal to make, but I do think that the
current patch-queue process is not suited to the project as it stands
today. Maybe if this issue-tracking stuff gets off the ground, we
could let developers place
.
Joshua D. Drake
//Magnus
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com
Magnus Hagander wrote:
PostgreSQL will also not recover on its own (e.g; auto restart and
roll through the logs).
What do you mean by this? It doesn't start upon reboot?
What is needed
to make it start?
It means that postgresql doesn't recover on its own. On linux
if a backend crashes all of
Josh failed to answer the most important question though:
Sorry.
Subsequent connections to the database will fail (such as pgAdmin)
and Windows must be completely rebooted.
Fail in what way. Hang, not connect, or get an error msg?
Just verified with customer. Once the problem occurs
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
Fail in what way. Hang, not connect, or get an error msg?
Just verified with customer. Once the problem occurs the first time, the
customer will continually get the same error message for each subsequent
connection attempt:
server
Alvaro Herrera wrote:
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
Fail in what way. Hang, not connect, or get an error msg?
Just verified with customer. Once the problem occurs the first time, the
customer will continually get the same error message for each subsequent
Alvaro Herrera wrote:
Joshua D. Drake wrote:
Alvaro Herrera wrote:
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
Fail in what way. Hang, not connect, or get an error msg?
Just verified with customer. Once the problem occurs the first time, the
customer will continually get
Alvaro Herrera wrote:
Joshua D. Drake wrote:
Alvaro Herrera wrote:
Joshua D. Drake wrote:
Alvaro Herrera wrote:
What I've been wondering all along is whether they are using a
connection pool.
Yes they are using a connection pool. A java based one.
It's quite possible that it's
Tom Lane wrote:
Dave Cramer [EMAIL PROTECTED] writes:
On 5-Sep-06, at 6:05 PM, Joshua D. Drake wrote:
Yes they are using a connection pool. A java based one.
Since java has it's own protocol implementation, this is totally
unrelated to any libpq error messages.
Another important point
Alvaro Herrera wrote:
Joshua D. Drake wrote:
Tom Lane wrote:
Dave Cramer [EMAIL PROTECTED] writes:
On 5-Sep-06, at 6:05 PM, Joshua D. Drake wrote:
Yes they are using a connection pool. A java based one.
Since java has it's own protocol implementation, this is totally
unrelated to any libpq
or after
authentication.
The only known resolution is to reboot Windows. Using the service
control panel to shutdown postgresql will fail once the message is
received. It is unknown if using the task master to individually kill
processes will work.
Sincerely,
Joshua D. Drake
.
The bottom line here is that all we have so far are client-side
observations (I get this message) and we have no clue what state
the postmaster thinks it's in. We really need more information.
Yes, unfortunately there isn't much more to be had for another 2 weeks ;)
Sincerely,
Joshua D
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
Yes, unfortunately there isn't much more to be had for another 2 weeks ;)
I trust they've got the reboot time and they will know exactly how long
from reboot to problem? I'm not all that sold on the GetTickCount
overflow theory
Gregory Stark wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
O.k. to recap:
This message will present itself, if connection attempts are made from the Web
Application (Java/JDBC), or locally via PgAdmin. Once the error message is
received, all subsequent connection attempts will also result
remember when they grabbed the snapshot.
Heh, o.k. I can definitely respect that :)
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions
PostgreSQL test people, but folks from Java and the like testing
other stuff. And they're pulling the build from ftp:/pub/dev/, not from CVS.
O.k. but why aren't they submitting pgsql-bugs?
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support
Bruce Momjian wrote:
I know I promised the release notes for today/Saturday, but a few other
things have taken my time. I will have a draft posted by
Monday/Tuesday. Sorry.
Thanks for the update.
J
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support:
% reduction in performance. Why
add to that? What we need to be doing is finding a way to decrease the
impact of foreign key checks.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing
take it. How long do I have?
Joshua D. Drake
regards, tom lane
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
Tom Lane wrote:
Seems like this area needs more attention ... anyone want to work on it?
I'll take it. How long do I have?
Since it's contrib, I don't think we need to hold you to being done
before beta1. But the sooner the better
,
Joshua D. Drake
cheers
andrew
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
. An additional item
that would be useful is to allow pg_restore to restore plain text dumps.
Sincerely,
Joshua D. Drake
regards, tom lane
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore
Bruce Momjian wrote:
Dave Page wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michael Fuhr
Sent: 12 September 2006 19:57
To: Bruce Momjian
Cc: PostgreSQL-development
Subject: Re: [HACKERS] Release notes
On Tue, Sep 12, 2006 at 02:31:22PM
If everything goes okay, I should be able to submit a beta patch for
reviewing during next two weeks (and get shot at :))
/me starts loading...
Regards,
Gevik
---(end of broadcast)---
TIP 1: if posting/reading through Usenet,
on input.
Not to come down on your hard work, but isn't the money type deprecated?
Joshua D. Drake
darcy=# select '$92,233,720,368,547,758.07'::money;
money
92,233,720,368,547,758.07
(1 row)
Index: src/backend/utils/adt/cash.c
D'Arcy J.M. Cain wrote:
On Thu, 14 Sep 2006 07:59:07 -0700
Joshua D. Drake [EMAIL PROTECTED] wrote:
D'Arcy J.M. Cain wrote:
For years I have been promising that a 64 bit version of the money type
was on the way. Here it is. So far it compiles and I have done some
basic testing
running on foo, skipping foo
Sincerely,
Joshua D. Drake
regards, tom lane
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED
Hello,
I know that this would be completely out of the norm. However, would it
be worth considering having a mid cycle release for 8.3?
Basically the release would focus on:
Updateable views
Bitmap indexes
Recursive queries
We would release in June?
Sincerely,
Joshua D. Drake
Stefan Kaltenbrunner wrote:
Joshua D. Drake wrote:
Hello,
I know that this would be completely out of the norm. However, would it
be worth considering having a mid cycle release for 8.3?
Basically the release would focus on:
Updateable views
Bitmap indexes
Recursive queries
We would release
why I said I frankly won't. I have customers with multi
terrabyte datasets. 8.1 performs wonderfully for them. It would be a
hard push to initiate an 8.2 outage for that.
Joshua D. Drake
Stefan
---(end of broadcast)---
TIP 4: Have you
D'Arcy J.M. Cain wrote:
On Thu, 14 Sep 2006 08:17:29 -0700
Joshua D. Drake [EMAIL PROTECTED] wrote:
Obviously ;), but it is deprecated by the project.
I keep hearing that but no action is ever taken. I think that there
are too many people who still find it useful.
By the way, I removed
that is involved with postgresql, I could
easily see almost a full man year lost, by having freeze where it is now.
I think having a freeze more toward march/april makes a heck of a lot of
sense.
Joshua D. Drake
regards, tom lane
--
=== The PostgreSQL Company
Stephen Frost wrote:
* Joshua D. Drake ([EMAIL PROTECTED]) wrote:
Updateable views
Bitmap indexes
Recursive queries
We would release in June?
Could we get autovacuum enabled by default too?
I certainly hope not... I don't really feel like turning it off all the
time.
Joshua D. Drake
lazy, and I don't want to
actually evaluate my needs. Lets just go with MS Access
Joshua D. Drake
Thanks,
Stephen
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most
but it isn't that big of a deal.
Take care.
Joshua D. Drake
Joshua D. Drake
Thanks,
Stephen
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL
No one would expect Oracle to install Oracle and walk away. We are not
MySQL, nor MS Access.
I can definitely see where you're coming from, it's a sort of tough-love
scenario. There are legitimate counter arguments, though. The most
obvious is that anyone who *does* evaluate their needs
Tom Dunstan wrote:
Joshua D. Drake wrote:
No one would expect Oracle to install Oracle and walk away. We are not
MySQL, nor MS Access.
And thank goodness for that!
Hah! I knew you would eventually agree with me. ;)
Joshua D. Drake
Tom
---(end of broadcast
Alvaro Herrera wrote:
Joshua D. Drake wrote:
No one would expect Oracle to install Oracle and walk away. We are not
MySQL, nor MS Access.
Then why are you complaining about having to disable autovacuum after
each installation?
Because my hands hurt and I can't find my gloves. My back hurts
Guido Barosio wrote:
Let me know if you need an extra pair of eyes.
O.k. I do :) Writing the scripts up are easy enough, but I am unsure how
the whole make file foo works...
Joshua D. Drake
G.-
On 9/10/06, Joshua D. Drake [EMAIL PROTECTED] wrote:
Tom Lane wrote:
Joshua D. Drake
.
Does anyone else have any opinions on this?
Does +1 count?
Joshua D. Drake
-Neil
---(end of broadcast)---
TIP 6: explain analyze is your friend
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564
provided any. You don't like $$, o.k. do you have a better solution?
What is the problem with timestamp?
Joshua D. Drake
best regards
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
a good honey moon and we look forward to having
you back in a couple of weeks!
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since
idea.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
---(end
have things we don't already know.
I am just going to hope that you are kidding about this one.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive
Jim C. Nasby wrote:
On Thu, Sep 14, 2006 at 02:36:22PM -0700, Joshua D. Drake wrote:
But on a serious note, the problem I run into is exactly the opposite.
Someone will turn on autovacuum because they thought it was a good idea
and for their work load, it isn't. So instead of creating new
1. Authorized user: is that someone with an account, or someone who has
been authorized by someone else?
In my mind it is someone who without threw a process of email
confirmation. Just to help stave off the amount of trolling that may happen.
Joshua D. Drake
2. I can see the official
and didn't even read the text after.
Why?
Because the text after a login failure or cancel when using httpd auth
is almost ALWAYS telling me I need a correct login. Not giving a link to
login.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support
would actually create
an account and be email confirmed.
Joshua D. Drake
//Magnus
---(end of broadcast)---
TIP 6: explain analyze is your friend
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564
Gregory Stark wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
1. Authorized user: is that someone with an account, or someone who has
been authorized by someone else?
In my mind it is someone who without threw a process of email confirmation.
Just to help stave off the amount of trolling
with pgbugs.commandprompt.com.
We could always use a couple more.
Joshua D. Drake
cheers
andrew
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http
Jim C. Nasby wrote:
On Sun, Sep 17, 2006 at 12:32:13PM -0700, Joshua D. Drake wrote:
Tom proposed a modest roadmap type experiment a week or so ago. I'd like
to see that pursued. After all, we know of some things that are at least
at first cut stage for 8.3, and a few things high on may
D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
---(end of broadcast
, no?
No. 8.1 did not have it turned on by default.
Sincerely,
Joshua D. Drake
Regards,
Andreas
---(end of broadcast)---
TIP 6: explain analyze is your friend
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support
Gregory Stark wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
No. 8.1 did not have it turned on by default.
Neither does 8.2 though.
oh... heh.
J
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
, you'll do a lot better to get the community involved sooner.
Thanks for your opinion, but I disagree completely.
History in this community has basically shown that although you disagree
you are completely wrong. Good luck with your project.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL
:-)
This will likely stop people from migrating to 8.2, but so what? It
isn't going to stop new users and existing users in real production
setting will likely wait for 8.3 anyway.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7
research, just fire off ab.
Using a DOS to attack *any* database server via the web is a 3 second
command.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL
Jim C. Nasby wrote:
On Fri, Sep 22, 2006 at 11:58:04AM -0500, Bruno Wolff III wrote:
On Wed, Sep 13, 2006 at 22:22:12 -0700,
Tom Dunstan [EMAIL PROTECTED] wrote:
That's a worthwhile point. How many patches come from the general
community vs out of the blue? Patches from regulars could
problems,
and maybe much more. Thoughts?
I think that 128 megs is probably a reasonable starting point. I know
plenty of people that run postgresql on 512 megs of ram. If you take
into account shared buffers and work mem, that seems like a reasonable
starting point.
Joshua D. Drake
that RH's
kernel hackers might not be too excited about investigating. (Alan Cox,
for one, has got other things to worry about this weekend:
http://zeniv.linux.org.uk/%7etelsa/boom/
Uhmm... doh?
Joshua D. Drake
I believe Dan's busy updating his kernel --- if a current Suse kernel
still shows
on large sets like this but
that might be overkill anyway.
You could dial down client_min_messages, set it to ERROR, then you won't
see warnings ;)
Sincerely,
Joshua D. Drake
Thanks,
Stephen
---(end of broadcast
Marc G. Fournier wrote:
On Sat, 23 Sep 2006, Walter Cruz wrote:
There's a date to postgreSQL 8.2 final?
Figure 45-60 days, but not a firm date ...
See Tom Lane's post.
Joshua D. Drake
---(end of broadcast)---
TIP 1: if posting/reading
Bruce Momjian wrote:
Joshua D. Drake wrote:
Guido Barosio wrote:
Let me know if you need an extra pair of eyes.
O.k. I do :) Writing the scripts up are easy enough, but I am unsure how
the whole make file foo works...
OK, are all the uninstall scripts done?
Crap... yes they are, at least
the
*additional* authentication methods.
Is there any reason why we haven't built a generic authentication API?
Something like PAM, except cross platform?
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
Is there any reason why we haven't built a generic authentication API?
Something like PAM, except cross platform?
We're database geeks, not security/crypto/authentication geeks. What
makes you think we have any particular competence
Joshua D. Drake wrote:
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
Yes, unfortunately there isn't much more to be had for another 2
weeks ;)
I trust they've got the reboot time and they will know exactly how long
from reboot to problem? I'm not all that sold
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
O.k. further on this.. the crashing is happening quickly now but not
predictably. (as in sometimes a week sometimes 2 days).
OK, that seems to eliminate the GetTickCount-overflow theory anyway.
That log entry is the last
701 - 800 of 2933 matches
Mail list logo
