pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedMail about select
2+ messages / 2 participants
[nested] [flat]
* Mail about select
@ 1999-06-04 08:01 Vikrant Rathore <vikrant@chemquick.com>
1999-06-04 14:33 ` Re: [SQL] Mail about select Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 2+ messages in thread
From: Vikrant Rathore @ 1999-06-04 08:01 UTC (permalink / raw)
To: pgsql-sql@hub.org
Dear Friends,
I have two tables
1. "Radius"
Table = radius
+----------------------------------+----------------------------------+-------+
| Field | Type |
Length|
+----------------------------------+----------------------------------+-------+
| uname | char()
| 256 |
| logdate | date
| 4 |
| logtime | time
| 8 |
| duration | int4
| 4 |
| status | char()
| 20 |
| nasadd | char()
| 20 |
| port | int4
| 4 |
| bytesin | int4
| 4 |
| bytesout | int4
| 4 |
| packin | int4
| 4 |
| packout | int4
| 4 |
| misc | int4
| 4 |
+----------------------------------+---------------------------------
2) "radiustemp" with the same structure
now i am firing a query like this:
select r.uname from radius r, radiustemp rt where r.uname<>rt.uname and
r.logdate<>rt.logdate and r.logtime<>rt.logtime;
After some time i get response
"Segmentation Error"
core(sumped)
can any one help what is the error in this query.
Thanks in advance for your kind help.
Regards,
Vikrant
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: [SQL] Mail about select
1999-06-04 08:01 Mail about select Vikrant Rathore <vikrant@chemquick.com>
@ 1999-06-04 14:33 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 1999-06-04 14:33 UTC (permalink / raw)
To: vikrant@chemquick.com; +Cc: pgsql-sql@hub.org
Vikrant Rathore <vikrant@chemquick.com> writes:
> now i am firing a query like this:
> select r.uname from radius r, radiustemp rt where r.uname<>rt.uname and
> r.logdate<>rt.logdate and r.logtime<>rt.logtime;
> After some time i get response
> "Segmentation Error"
> core(sumped)
How big are your tables? That query will probably produce an output
row for almost every combination of a row from radius with a row from
radiustemp, which might overflow the allowed memory for your
application.
I suppose what you really want is to find the rows in radius that do
not have duplicates in radiustemp, but that query won't do it...
regards, tom lane
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~1999-06-04 14:33 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-06-04 08:01 Mail about select Vikrant Rathore <vikrant@chemquick.com>
1999-06-04 14:33 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox