Hi,
postgresql 7.0.2. Why by executing the following query
select * from magazine
where id in (
select mag_id from dict where word = 'akademie' intersect
select mag_id from dict where word = 'der' intersect
select mag_id from dict where word = 'klasse' )
I receive the followin
On Tue, Aug 22, 2000 at 01:50:26PM +0400, Alex Guryanow wrote:
> Hi,
>
> postgresql 7.0.2. Why by executing the following query
>
> select * from magazine
> where id in (
> select mag_id from dict where word = 'akademie' intersect
> select mag_id from dict where word = 'der' intersec
Folks,
We posted the following announcement on our website today, at
http://www.greatbridge.com/news/press.html.
Please feel free to email me off-list with any questions.
Thanks,
Ned
UPDATE, August 22, 2000:
MySQL performance improves with tuning suggestions from development
team;
PostgreSQ
It would be interesting to see how well PostgreSQL performed when it was
tuned.
Or has it allready been tuned?
Ned Lilly wrote:
> Folks,
>
> We posted the following announcement on our website today, at
> http://www.greatbridge.com/news/press.html.
>
> Please feel free to email me off-list with
A thanks to everyone on this list and especially; Jeffery Rhines, Chris
Knight, Chris Bitmead, and Sevo Stille.
The solution turned out to be very simple. After catching a SCSI BUS
speed mismatch problem which caused a NT Backup 'Restore' failure I
discovered that the actual data was in .mdb fil
Le 22.08.00 a 09:37, "Roderick A. Anderson" m'ecrivait :
)I was able to get the table format by using MS Access. Only question left
)is what is the corresponding field type in PostgreSQL for a memo field in
)SQL Server/Access (varchar())?
'text' type perhaps ?
Lionel
At 4:26 PM -0400 8/21/2000, Tom Lane wrote:
>Michael Blakeley <[EMAIL PROTECTED]> writes:
>> Do I need to tell postgres to rebuild pg_language, perhaps?
>
>See the createlang utility script. PL languages aren't installed
>by default (due to possibly-overzealous concern about security).
Thanks -
I hate it when I do this. See an answer I want and run with it rather
than find the real answer.
Turned out the data files (.mdb) _didn't_ belong to the database. They
were a piece of the database that was used for a report.
Back to the old grind wheel.
Rod
--
Roderick A. Anderson
[EMAIL PRO
In mysql you can make some data apear to be garbled
or hiddne, I'm wondering if this can be done using
psql?
Tressens Lionel <[EMAIL PROTECTED]> writes:
> Le 22.08.00 a 09:37, "Roderick A. Anderson" m'ecrivait :
> )I was able to get the table format by using MS Access. Only question left
> )is what is the corresponding field type in PostgreSQL for a memo field in
> )SQL Server/Access (varchar())?
>
I've seen brief posts regarding server loads, distrubution for heavy loads,
etc, but don't recall if there were any solutions...
Anyways...We are running a Postgres DB against multiple frontend
webservers. For most of the time, everything runs fine. Then, all of a
sudden, everything will sta
Hi,
I was wondering if there is a way to have a foreign key reference to the
primary key column of all tables throughout an inheritance tree. For
example, I have a parent_table with a unique_id (type serial) and a child
table which inherits the parent_table (inheriting the unique_id). I woul
you could "hide" or mask columns through views...
mikeo
At 02:10 PM 8/22/00 -0700, Mike Sears wrote:
In mysql you can make some data apear to be garbled or hiddne, I'm wondering if this can be done using psql?
"Arthur M. Kang" <[EMAIL PROTECTED]> writes:
> When I log onto the DB server and try to do anything, I get "Too many open
> files in system."
Sounds like you need to regenerate your kernel with larger NFILE and/or
NINODE parameters. Can't give you details about how to do this since
every Unix p
> I've seen brief posts regarding server loads, distrubution for heavy
loads,
> etc, but don't recall if there were any solutions...
>
> Anyways...We are running a Postgres DB against multiple frontend
> webservers. For most of the time, everything runs fine. Then, all of a
> sudden, everything
On Tue, 22 Aug 2000, Tom Lane wrote:
> Tressens Lionel <[EMAIL PROTECTED]> writes:
> > Le 22.08.00 a 09:37, "Roderick A. Anderson" m'ecrivait :
> > )I was able to get the table format by using MS Access. Only question left
> > )is what is the corresponding field type in PostgreSQL for a memo fie
I've wondered that myself, actually. What are the benefits and
drawbacks to going with one over the other, besides the obvious 255-char
field length limit for varchar? The reason to stay away from "memo"
fields in other serious RDBMSs are typically more difficult maintenance,
significantly lower
See http://www.greatbridge.com/news/p_081620001.html - we increased the
cache, ran a vacuum analyze, a few minor things.
Regards,
Ned
"Poul L. Christiansen" wrote:
> It would be interesting to see how well PostgreSQL performed when it was
> tuned.
>
> Or has it allready been tuned?
>
> Ned Lill
On Tue, 22 Aug 2000, Darrin Ladd wrote:
> Hi,
>
> I was wondering if there is a way to have a foreign key reference to the
> primary key column of all tables throughout an inheritance tree. For
> example, I have a parent_table with a unique_id (type serial) and a child
> table which inherits
Having a slight problem w/ my postgres database.
for some reaons its no longer updating anymore, and for what reason I'm
unsure
if I'm right then the below "should" update the
table I'm working in, though it doesn't. Is ther indeed something wrong
here?
require("dbconect.inc.php");
$resu
> Mike Sears wrote:
>
> Having a slight problem w/ my postgres database. for some reaons its
> no longer updating anymore, and for what reason I'm unsure
>
> if I'm right then the below "should" update the table I'm working in,
> though it doesn't. Is ther indeed something wrong here?
>
> requ
many thanks both andrew and ryan =)
- Original Message -
From: "ryan" <[EMAIL PROTECTED]>
To: "Mike Sears" <[EMAIL PROTECTED]>
Cc: "pgsql-general" <[EMAIL PROTECTED]>
Sent: Tuesday, August 22, 2000 2:40 PM
Subject: Re: [GENERAL] php update problems
> > Mike Sears wrote:
> >
> > Having
Martijn van Oosterhout wrote:
>
> We used pg_dump in various ways, all with the date style "iso"
> but always some of the dates appeared to be translated wrong.
> Eventually we worked out that even though the datestyle was
> set to "iso" on both machines, the old postgres read it as
> "ISO with e
23 matches
Mail list logo