Hi there,
I'm migrating from MySQL to PostgreSQL and I was wondering whether someone
could help me match some datatypes.
I'm also migrating, and would appreciate any thoughts on how to do
it. Spesifically, if there could be any problems with functions not
supported on the PostgreSQL and
That's odd. This is the error I got compiling pgsql 6.5 on Solaris. I
never resolved the problem. However, the 7.0 source did not give this
error. Maybe this is a stupid question, but are you sure you have the
most recent source code?
First of all, thank you very much for this detailed answer. (and also thanx
to Janet for asking :-] ) I am a postgresql newbie as well, and this is
very very helpful. I had been trying to get things to work under NT, but
decided to reboot to linux and try it there when I saw these detailed
Uh, I cut pasted the transcript in two pieces to get the selects in
the same order, and messed up. The error happens _after_ connecting as
anonymous, not before.
Ross
On Wed, May 24, 2000 at 01:09:58PM -0500, Ross J. Reedstrom wrote:
idas= select count(*) from urls;
ERROR: urls:
I've remarked that postgresql-7.0 have two important bugs no, no...
I'll define its Problems.
The first is that it is very subsceptible to ipc: it's true that sometimes
U need to do an ipcclean to remake it start
The second is the very VERY important instability problem.
I explain me better:
On Mon, 15 May 2000 23:04:48 +0100 Joe Karthauser wrote:
And last but not least I'm used to using the 'desc tablename' sql command
to show the structure of a table within MySQL. How do I do the same in
PostgreSQL.
In psql "\i tablename". Check out \? or the documentation for all the
On Thu, May 25, 2000 at 04:58:48AM +1000, Giles Lean wrote:
On Mon, 15 May 2000 23:04:48 +0100 Joe Karthauser wrote:
And last but not least I'm used to using the 'desc tablename' sql command
to show the structure of a table within MySQL. How do I do the same in
PostgreSQL.
In psql
Hello everyone! :)
This little problem is bothering me a lot! It seems that PostgreSQL 7.0
uses different semantics than Oracle when evaluting SQL?!
I have two relations, A and B, both containing the attributes "number"
(int) and "amount" (int). There's no primary key, and the two relations
Joe Karthauser wrote:
Hi there,
I'm migrating from MySQL to PostgreSQL and I was wondering whether someone
could help me match some datatypes.
I'm trying to learn PostgreSQL myself. They say there's no better way
to learn than to teach, so here goes...
Firstly MySQL has a 'timestamp'
On Wed, 24 May 2000 14:26:32 -0500 "Ross J. Reedstrom" wrote:
Actually, it's "\d tablename". The rest is right, though.
Teach me to try to tidy things up before posting won't it?
Thanks!
Giles (sigh, time for coffee)
On Wed, 24 May 2000, planx plnetx wrote:
I've remarked that postgresql-7.0 have two important bugs no, no...
I'll define its Problems.
The first is that it is very subsceptible to ipc: it's true that sometimes
U need to do an ipcclean to remake it start
This sounds like a Linux problem
On Wed, 24 May 2000, The Hermit Hacker wrote:
On Wed, 24 May 2000, planx plnetx wrote:
I've remarked that postgresql-7.0 have two important bugs no, no...
I'll define its Problems.
The first is that it is very subsceptible to ipc: it's true that sometimes
U need to do an ipcclean
I have a large report that I run once a day. Under 6.5.3 it took just over
3hrs to run. Under 7.0 it is now taking 8 hours to run. No other changes
were made.
This is on RedHat Linux 6.2. A PIII 733 with 384MB Ram, and 2 IDE 7200 RPM
disks. One disk contains the Postgres directroy including
Hi- I'm a newbie at postgres but have a pretty good
understanding of SQL statements. I have created two
views and wanted to do a LEFT OUTER JOIN of the two
tables. The sytax is
select * from vcompany LEFT OUTER JOIN ON
vcompany.id=vregistry.id;
I get the following error:
LEFT OUTER JOIN not
Peter Landis wrote:
Hi- I'm a newbie at postgres but have a pretty good
understanding of SQL statements. I have created two
views and wanted to do a LEFT OUTER JOIN of the two
tables. The sytax is
select * from vcompany LEFT OUTER JOIN ON
vcompany.id=vregistry.id;
I get the
"planx plnetx" [EMAIL PROTECTED] writes:
FATAL 1: cannot create init file
mydatabasedirectory//base/mydb/pg_internal.init
If you're getting that, there is something *seriously* broken ---
the only way that can come out is if Postgres is unable to create
that file when it wants to. I wonder
Travis Bauer [EMAIL PROTECTED] writes:
That's odd. This is the error I got compiling pgsql 6.5 on Solaris. I
never resolved the problem. However, the 7.0 source did not give this
error. Maybe this is a stupid question, but are you sure you have the
most recent source code?
On Tue, 23
"Bryan White" [EMAIL PROTECTED] writes:
Top tells me the front end process is using 5 to 10 percent of the CPU and
the back end is using 10 to 20 percent. The load average is about 1.0 and
the CPU is about 80% idle.
It's probably waiting for disk I/O ...
What does EXPLAIN tell you about how
Try putting 'nofsync' in your pg_options.
Bryan White wrote:
I have a large report that I run once a day. Under 6.5.3 it took just over
3hrs to run. Under 7.0 it is now taking 8 hours to run. No other changes
were made.
This is on RedHat Linux 6.2. A PIII 733 with 384MB Ram, and 2
Ooops. I have to withdraw that comment. I spent hours the other day
beating my head against the wall over this. I was sure that it didn't
work . . .
Sorry,
Travis Bauer | CS Grad Student | IU |www.cs.indiana.edu/~trbauer
I'm not telling that I've chanced this or that:
I am telling that only with compiling the postgresql7.0 updating the
RC1 it give me this (with the same SETTINGZ pgdata,pglibs,sqladmin,etc...
the SAME!) on an other machine the 7.0definitive go directly in core
dumped with kernel 2.2.14 and
First of all,
Let me say I dont have much experience with postgresql and I've
done only few tests, so excuse me for any wrong comments i make.
I think the following things should be improved in postgresql now:
- reliability
- Documentation
Sometimes a table doesnt exist anymore but it's still
22 matches
Mail list logo