"Patrick Hatcher" <[EMAIL PROTECTED]> writes:
> I'm not sure this is a PgAdminIII error or a Pg 7.3.5 error
Seems like it must be PgAdmin issuing some bogus query. I'd suggest
taking it up on their mailing list ...
regards, tom lane
---(end of bro
Mira como se domina a postgresql para que trabaje en una aplicacion hecha en Visual Basic 6.0 y el usuario final no tiene que hacer nada para subir y bajar el servicio
www.compraventas.coms.ph
Para que no tengas que invertir en un servidor solo para linux
Look Postgresql under a Windows App.
I'm not sure this is a PgAdminIII error or a Pg 7.3.5 error
I've created the following table:
CREATE TABLE public.prod_manager
(
mgmid varchar(6) NOT NULL,
mgmname varchar(35),
email varchar(50) NOT NULL,
CONSTRAINT prdmg_pk PRIMARY KEY (mgmid)
) WITHOUT OIDS;
with the following data
ins
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> No we don't, because we set the rpath and our installation routines take
> care that in the target directory the libfoo.so.X is in fact the latest
> library. The only problem that make check has is that it bypasses the
> prober installation routine
Here is a freebie for MacOSX users... BiggerSQL is a postgresql
browser and more. Only tested on MacOS X 10.3.2 and Postgresql 7.4.1.
Cocoa source is part of the package. I understand that BiggerSQL
might need to be rebuilt if your backend is not compatible with
the 7.4 release. The program links w
Tom Lane wrote:
> On investigation, I can't find any sign that my Linux box does
> anything with library minor version numbers either. That seems to
> mean that we should be bumping the major version for every release
> (unless we made no externally visible changes at all, not even
> upward-compat
Hi all,
Necessary to inside insert archives (jpg, doc) of the bd using delphi +
DBExpress
How to make this?
Exists an example?
regards, fern
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
On Thu, Mar 11, 2004 at 09:43:57 +0100,
Paolo Tavalazzi <[EMAIL PROTECTED]> wrote:
> Alle 19:12, mercoledì 10 marzo 2004, hai scritto:
> > On Wed, Mar 10, 2004 at 18:33:41 +0100,
> >
> > Paolo Tavalazzi <[EMAIL PROTECTED]> wrote:
> > > I don't know what to make, help me please!
> > >
> > > Anot
Csaba Nagy <[EMAIL PROTECTED]> writes:
> Looks like there's no minor version info at all in the binaries, I would
> say...
On investigation, I can't find any sign that my Linux box does anything
with library minor version numbers either. That seems to mean that we
should be bumping the major vers
Paolo Tavalazzi <[EMAIL PROTECTED]> writes:
> [ query plans after updating to 7.4.2 ]
Okay, they're certainly a lot closer than before, so I think I was right
that you were getting bitten somehow by the pg_statistic alignment
problem. It seems like there may still be a bug lurking though. The
ro
On Thu, 2004-03-11 at 17:26, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> But shouldn't the minor-version bump between 7.3 and 7.4 libpq.so
> >> have prevented the dynamic linker from accepting the 7.3 libpq.so as
> >> the one to use? I thought the rule w
Alle 19:40, mercoledì 10 marzo 2004, hai scritto:
> Paolo Tavalazzi <[EMAIL PROTECTED]> writes:
> > I have applied the procedure for fixing pg_statistic as you had said,
> > but the result is the same!
>
> Hm. It could be a planner bug. Can you reproduce the misbehavior if
> you dump and load t
Paolo Tavalazzi <[EMAIL PROTECTED]> writes:
> But the query plans are still various!!
I think you made a copy-and-paste mistake, because the explain results
you posted are exactly the same ...
regards, tom lane
---(end of broadcast)
Tom Lane wrote:
> But shouldn't the minor-version bump between 7.3 and 7.4 libpq.so
> have prevented the dynamic linker from accepting the 7.3 libpq.so as
> the one to use? I thought the rule was "same major version as
> requested, minor version >= requested".
Maybe, but the directory search orde
Hi Joe;
thank a lot for the guide about the garbage character. I had copied and
pasted it before, but now I've retyped it by hand and it works perfectly.
This function will be very very useful for me.
Best regards,
Javier
-
El Mar
Alle 18:03, giovedì 11 marzo 2004, hai scritto:
> Paolo Tavalazzi <[EMAIL PROTECTED]> writes:
> > But the query plans are still various!!
>
> I think you made a copy-and-paste mistake, because the explain results
> you posted are exactly the same ...
>
> regards, tom lane
E
On Wed, 10 Mar 2004, Christopher Petrilli wrote:
> On Mar 10, 2004, at 3:14 PM, Steve Wolfe wrote:
>
> >Before I shell out the $15k on the 4-way Opteron, I'm going to spend
> > some long, hard time looking for ways to make the system more
> > efficient.
> > However, after all that's already
[snip]
> The problem was that the new psql was linking to an older version of
> libpq.so (one that doesn't export get_progname()). As best I can tell
> that would have had to be a 7.3 libpq.so, which means there is something
> wrong here because the 7.3 libpq should have had a different minor
> nu
> "SW" == Steve Wolfe <[EMAIL PROTECTED]> writes:
SW> However, after all that's already been done, I'm not optimistic that it's
SW> going to preclude needing the new server. I'm just surprised that nobody
SW> seems to have used PostgreSQL on a quad-Opteron before!
I think people saturate the
With mem per CPU, Opterons scale very well in most cases (as long as you
have many processes). The lower memory latency helps too.
Is it likely for you to be network bandwidth limited - e.g. maxing out your
NICs or NIC I/O capacity? I doubt it, but if you are actually getting close
then things
20 matches
Mail list logo