Question for anyone...
I have to queries. One runs in about 2 seconds. The other takes upwards
of 2 minutes. I have a temp table that is created with 2 columns. This
table is joined with the larger database of call detail records.
However, these 2 queries are handled very differently.
The queries
Rob Schall <[EMAIL PROTECTED]> writes:
> I have to queries. One runs in about 2 seconds. The other takes upwards
> of 2 minutes. I have a temp table that is created with 2 columns. This
> table is joined with the larger database of call detail records.
> However, these 2 queries are handled very di
The following bug has been logged online:
Bug reference: 3089
Logged by: Andrew White
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: SuSE Linux 9
Description:View/Table Creation/Ownership Bug
Details:
To Whom It May Concern,
I came acr
The following bug has been logged online:
Bug reference: 3083
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: Windows 2000
Description:Installation to path with umlaufs fails with initdb
Details:
Install Postgres to a path like
The following bug has been logged online:
Bug reference: 3086
Logged by: Akio Iwaasa
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.8
Operating system: Redhat EL ES 3.0
Description:DBMirror's error (SERIAL attribute)
Details:
I'm sorry for my poor English.
The following bug has been logged online:
Bug reference: 3093
Logged by: Ilya Storozhilov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: FreeBSD 6.1-RELEASE-p10 #1
Description:Error with converting error messages between server and
client
The following bug has been logged online:
Bug reference: 3087
Logged by: Michael Witten
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: Mac OS X 10.4.8
Description:Endiannes, of all things
Details:
I'm in a relatively foul mood, but I'll
The following bug has been logged online:
Bug reference: 3085
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: FreeBSD 6.1
Description:Performance BUG
Details:
Test sequence:
%psql test
create table t1 (i4 int4);
insert into t
Dear Team,
I checked the shortcut and was unable to find any note about "close on exit" or
anything like that. The .bat method sounds wonderful, and I would appreciate
such a change to make the product a little more responsive.
Thank you for your consideration and time,
Raymond Naseef
P.S.
The following bug has been logged online:
Bug reference: 3092
Logged by: Andrew Rass
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: FreeBSD 6.2
Description:character varying and integer cannot be matched
Details:
Hello the following pro
Andrew Rass wrote:
> ERROR: IN types character varying and integer cannot be matched
> SQL Status:42804
Please provide the complete table definitions necessary to reproduce the
problem.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)--
Michael Witten wrote:
> Now I have to issues all of these commands and follow all of these
> protocols when a simple copy should have done the trick.
What is your point? Complain to your CPU manufacturer if you don't like
how they lay out data in memory.
--
Peter Eisentraut
http://developer.po
Ilya Storozhilov wrote:
> 1. Create database in UTF8 encoding
You have likely forgotten to set a matching locale.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will
"Andrew White" <[EMAIL PROTECTED]> writes:
> I came across an interesting issue regarding views and ownership that I
> think may be a bug in PG. I am using PG 8.2.3 on SuSE Linux.
AFAICS this is behaving as intended, because you did not grant select on
the underlying table to the owner of the v
"" <[EMAIL PROTECTED]> writes:
> Description:Performance BUG
You haven't actually shown us any bug. These are not the same query and
there's no reason to expect them to take the same amount of time.
regards, tom lane
---(end of broadcast)-
"Andrew Rass" <[EMAIL PROTECTED]> writes:
> ERROR: IN types character varying and integer cannot be matched
> postgresql 7.4.7 did this
> and now it did this problem like describe
This is not a bug; it's an intentional tightening of the behavior.
You'll need to put in a cast so that the system kn
On 1 Mar 2007, at 11:17:16 AM, Peter Eisentraut wrote:
Michael Witten wrote:
Now I have to issues all of these commands and follow all of these
protocols when a simple copy should have done the trick.
What is your point? Complain to your CPU manufacturer if you don't
like
how they lay out
the PGDG .rpm's for RHEL4 have a bit of an annoyance...
RHEL4 ships with postgres 7.4.x, and various RHEL4 RPMs have a
dependency on libpq.so.3 ...
# rpm -Uvh postgresql-8.2.3-1PGDG.i686.rpm \
> postgresql-libs-8.2.3-1PGDG.i686.rpm \
> postgresql-server-8.2.3-1PGDG.i686.rpm \
> postgresql-
John R Pierce wrote:
RHEL4 ships with postgres 7.4.x, and various RHEL4 RPMs have a
dependency on libpq.so.3 ...
Using the CentOS 4 base repository, I've identified these RPMs as
depending on libpq.so.3, which is obsoleted and removed by the
postgresql-libs-8.2.3-1PGDG RPM ...
cyrus-sasl
19 matches
Mail list logo
