On Mon, 25 Jun 2001, Bruce Momjian wrote:
> > On Mon, 25 Jun 2001, Bruce Momjian wrote:
> > > > Is RedHat simply providing PostgreSQL support or are they
> > > > placing developers to work on enhancements/bug fixes as well?
> > >
> > > They are placing developers too. New people. I assume they
"Thalis A. Kalfigopoulos" <[EMAIL PROTECTED]> writes:
> Always a first time for everything bad. Anyway, not wanting to be the
> pessimist of the bunch, I'll hold my horses and hope that none of my
> "fears" turns into reality. The issue is that none of the other open
> source projects RH supporte
On Mon, 25 Jun 2001, Tom Lane wrote:
> "Thalis A. Kalfigopoulos" <[EMAIL PROTECTED]> writes:
> > I noticed that doing a join with the INNER JOIN ON... syntax gives a different
>execution plan (for complex queries at least) than when using the ',' syntax with the
>join conditions in the WHERE cl
"Thalis A. Kalfigopoulos" <[EMAIL PROTECTED]> writes:
> Changing the type of "join" syntax affects the plan-generation time
> and the execution-time. Would it be logical to EXPLAIN the query once
> using the 'FROM a,b,c WHERE...' syntax and then assuming that it
> returns the optimal execution pla
On 25 Jun 2001, Trond Eivind [iso-8859-1] Glomsrød wrote:
> "Thalis A. Kalfigopoulos" <[EMAIL PROTECTED]> writes:
>
> > Always a first time for everything bad. Anyway, not wanting to be the
> > pessimist of the bunch, I'll hold my horses and hope that none of my
> > "fears" turns into reality. T
On Mon, 25 Jun 2001, Bruce Momjian wrote:
> > On Mon, 25 Jun 2001, webb sprague wrote:
> >
> > > I guess I prefer my free software free...
> >
> > Agreed, but alot of companies want to be able to point a finger at
> > someone or some company when something goes awry. With RH being
> > the first
"Thalis A. Kalfigopoulos" <[EMAIL PROTECTED]> writes:
> On 25 Jun 2001, Trond Eivind Glomsrød wrote:
>
> > "Thalis A. Kalfigopoulos" <[EMAIL PROTECTED]> writes:
> >
> > > Always a first time for everything bad. Anyway, not wanting to be the
> > > pessimist of the bunch, I'll hold my horses and
That limit can also be raised by changing a constant and recompiling Apache;
8190 is just the default. Check the online docs for LimitRequestLine at
httpd.apache.org.
"Bryan White" <[EMAIL PROTECTED]> on 06/25/2001 02:59:30
PM
To: "Frank Hilliard" <[EMAIL PROTECTED]>,
"psql-general
On 25 Jun 2001, Trond Eivind [iso-8859-1] Glomsrød wrote:
> "Thalis A. Kalfigopoulos" <[EMAIL PROTECTED]> writes:
>
> > On 25 Jun 2001, Trond Eivind Glomsrød wrote:
> >
> > > "Thalis A. Kalfigopoulos" <[EMAIL PROTECTED]> writes:
> > >
> > > > Always a first time for everything bad. Anyway, not
EXPLAIN'ing the very simple query:
SELECT * FROM experimentsc WHERE expid=12;
I get the following plan:
NOTICE: QUERY PLAN:
Index Scan using experimentsc_expid_i on experimentsc (cost=0.00..2.01 rows=1
width=44)
EXPLAIN
I have two indeces on the same thing: expid (don't as why :^) One is
"Thalis A. Kalfigopoulos" <[EMAIL PROTECTED]> writes:
> Why exactly is experimentsc_expid_i chosen over experimentsc_pkey?
There is no reason to prefer either one over the other. So you get
a quasi-random choice (whichever one the optimizer happens to consider
first, I think).
Hi,
Can someone please tell me how to figure the optimal value of SHMMAX? I
have not been able to find this information in the docs.
Thanks,
sb
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscrib
It's not in the docs because it has to do with the use you make of your OS. The docs
only mention that shmem is used by Pg so increasing it could benefit you. The rule of
thumb (last week's list archives) is to tell postgres on startup to use shmem
equivalent to approximately 1/4 of you total m
On Tue, 26 Jun 2001, Andrew Snow wrote:
>
> > Yes, but are they going to be collaborating closely with the
> > current Pg core devel team or are they going to work on their
> > own? The concern is regarding the Cnet article about "Redhat
> > forking off eventually with their own pg". Their repre
Ed Loehr <[EMAIL PROTECTED]> writes:
> I am trying out postgresql 7.1.2. I'm experiencing a hung server on
> linux 2.4.2-2 when I run a sql script that drops & reloads many PL/pgSQL
> functions and triggers, as well as hanging during VACUUM ANALYZE.
Are you sure it's hung, and not just waiting o
Lamar Owen wrote:
>>ACTION: copy 109,128 characters into a phpPgAdmin "Edit" text entry box.
>>
>
>>RESULT: phpPgAdmin cuts off the copy at 28,652 characters [no more
>>accepted in box]
>>UPDATE EMPTY text cell:
>>RESULT: accepted [that is, it accepted 28,652 characters]
>>
>
> Most br
Thalis A. Kalfigopoulos wrote:
>>>
>>Well, if they fork then we can probably assume Redhat's database will be as
>>bad as their OS, so there's nothing to worry about ;-) *chuckle*
>>
>
> That's not true. If you started off with Ygdrassil linux then probably Rh seems too
>"soft", but they are t
17 matches
Mail list logo
