scott.marlowe wrote:
> Oh, spreading misinformation isn't lying? You live in a different
> world than I do.
Again, I apologise if you took my comment so strongly. I can understand when
something that someone works on so hard is critisised. OTOH however, your
original post that I replied to, was v
When grilled further on (Wed, 11 Feb 2004 01:03:50 -0500),
Tom Lane <[EMAIL PROTECTED]> confessed:
> Robert Creager <[EMAIL PROTECTED]> writes:
>
> Nothing on the backend side that I can think of. If you're using libpq
> then you could use PQtrace, though that's really intended for debugging
> l
Do constraints effect performance significantly?
Thanks
Jodi
--
___
Jodi L Kanter
BioInformatics Database Administrator
University of Virginia
(434) 924-2846
[EMAIL PROTECTED]
On Wed, 11 Feb 2004, Peter Galbavy wrote:
> scott.marlowe wrote:
> > Oh, spreading misinformation isn't lying? You live in a different
> > world than I do.
>
> Again, I apologise if you took my comment so strongly. I can understand when
> something that someone works on so hard is critisised. OT
On Wed, 11 Feb 2004, Jodi Kanter wrote:
> Do constraints effect performance significantly?
That depends.
Foreign key constraints on int4 columns or int8 columns (matching of
course) are usually quite fast.
FK constraints on non-int (numeric, text, etc...) tend to be slower.
check constraints
Mark Lubratt <[EMAIL PROTECTED]> writes:
> You mentioned that you'd see the problem during a large number of
> concurrent transactions. My question is, is this a necessary condition
> for the database crashing when the plug was pulled, or did you need use
> a large number of concurrent transact
How do I unsubscribe from this list.
I have tried everything including doing what it says at the bottom of
the messages about sending a message to majordomo with unsubscribe and
my email address as the header.
Nothing is working.
Please help.
Cheers
Tom
Tom Lane wrote:
Mark Lubratt <[EMAIL
Hi again,
I have started working on migrating my DBs from mysql to postgres today and
ran into a problem. When I type in psql, I get this error:
Welcome to psql 7.3.3, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? fo
To follow up on this, I just did try deleting those files and running the
RPM process again, and received the same errors.
rpm -ih postgresql-libs-7.4-0.3PGDG.i386.rpm
### [100%]
file /usr/lib/libpq.so.3 from install of postgresql-libs-7.4-0.3PGDG
conflicts
Or maybe rpm -Uvh postgresql-7.4.rpm
would work too.
---(end of broadcast)---
TIP 8: explain analyze is your friend
You need to rpm -e 'oldpostgresqlpackagenamehere' to get rid of 7.3 first.
On Wed, 11 Feb 2004, Jeremy Smith wrote:
> To follow up on this, I just did try deleting those files and running the
> RPM process again, and received the same errors.
>
> rpm -ih postgresql-libs-7.4-0.3PGDG.i386.rpm
> ##
scott.marlowe wrote:
> Log in as root, then "su - postgres" and type in "pg_autovacuum --help"
> and see if you get a response from that. If so, the the autovacuum
> daemon is there, and all you have to do to get it running it its basic
> format is to run it with 'pg_autovacuum -D'.
>
> On Tue
Thanks Lamar
I will try that link later, for some reason it's not coming up now. I tried
one of the FTPs off of the postgresql.org site, and the folder for 7.4.1 and
Redhat 7.3 was empty.
Btw, I have removed my RPM installation of 7.4.0, and my failed attempt at
installing 7.4.1 and am now left
On Wed, 11 Feb 2004, Jeremy Smith wrote:
> Thanks Lamar
>
> I will try that link later, for some reason it's not coming up now. I tried
> one of the FTPs off of the postgresql.org site, and the folder for 7.4.1 and
> Redhat 7.3 was empty.
>
> Btw, I have removed my RPM installation of 7.4.0, and
14 matches
Mail list logo
