Matt Beauregard <[EMAIL PROTECTED]> writes:
> prodex=# select category_id, category_name from category natural join
>category_product natural join product;
> pqReadData() -- backend closed the channel unexpectedly.
> That's the first time anything like this has happened... no doubt I
> have the
prodex=# select category_id, category_name from category natural join category_product
natural join product;
pqReadData() -- backend closed the channel unexpectedly.
This probably means the backend terminated abnormally
before or while processing the request.
The connection to th
Stephan Szabo <[EMAIL PROTECTED]> writes:
> As a separate issue I can't even do the query listed below on my
> machine with reasonably current sources, as it fails after a while with
> an ExecRestrPos: node type 18 not supported. Haven't looked yet...
Yes, there's a nasty little planning bug in
> How do I get rid of this error?
>
> Unrecognized variable client_encoding
>
> It is repeated with every psql command.
The message indicates the backend has been compiled without
--enable-multibyte option, but your frontend has been made with the
option. I guess you have mixed up two dif
I've been running 6.5.3 since March and it has never failed. That's
continuously since March too. Never more than 10 users at a time, and only
about 2 Gig data, but there it is, rock solid.
I would like to go to 7.something, but when you are having nothing but joy
and happiness, why change?
I've used PostgreSQL for pretty much any project I've required an RDBMS in
for the past 4+ years now ... VIEWs haven't figured very prominently in
that, but I can't really say that I've noticed any major problems with
unexpected crashes in the past 2 years or so ...
In the below, the user was do
Hi all,
I've just subscribed to the list this morning, as we are considering
installing Postgres for a particular project.
I guess I'm a little apprehensive, as perhaps coincidentally, this is the
second reference to unexpected crashes that I have heard in as many days .
Does this occur often
It was called out in the release notes for 7.0*
I got burned too...
Larry
* Geoff Russell <[EMAIL PROTECTED]> [000906 22:07]:
> Hi,
>
> Have I missed something, or has some date behaviour
> changed in going from 6.5.2 to 7.0.2?
>
> drop table tdate;
> create table tdate ( demo date );
> set
Just played with this a little bit, and I'm not 100% certain whether I'm
getting the "desired results", but why not do something like:
SELECT
stone_name, st.stone_uid, stone_modifies, stone_difficulty, stone_cost,
silver.jtyp_name AS silver_name, (silver.metal_cost + stone_cost) AS Expr1,
Hi,
Have I missed something, or has some date behaviour
changed in going from 6.5.2 to 7.0.2?
drop table tdate;
create table tdate ( demo date );
set DateStyle to 'European';
insert into tdate (demo) values ('31-12-1999');
set DateStyle to 'US'; select demo as US from tdate;
set DateStyle to 'E
For the record, I have a similar query in a program I developed that
aliases the same table multiple times and the performance on that one is
terrible as well. In fact, it's the only query of the many that program
uses that isn't downright snappy. Short of a table redesign (which I may
do anyway),
On Thu, 7 Sep 2000, Oliver Smith wrote:
> Each stone gives a specific set of attributes, but combining it with
> silver & plat gives one type of jewellery, while gold & electrum
> produce a different type.
>
> The reason for including this is so that a chart can be produced
> which shows what att
> OTOH, I'm not 100% sure what you're trying to get out
> from this query, I'd have expected that it would be, using
> these metals on this stone gives you this result, but since
> the types of jewelery I get are different on the same row
> of output, I'm a little confused.
Each stone gives a spe
Alexandre FLAMENT wrote:
>
> I made a table contenu, with idcontenu (of type serial) as
> primary key. A second table (image) inherits of contenu. The
> problem is the primary wasn't apply to the table image : I
> can insert two rows the same idcontenu. Is it normal ? How
> can I propagate the co
14 matches
Mail list logo
