On Friday 30 September 2005 15:23, Peter Eisentraut wrote:
> Am Freitag, 30. September 2005 09:03 schrieb Oliver Siegmar:
> > - Would it be possible to add a feature to PostgreSQL to allow grouping
> > by unique identifiers only?
> > - Is this requirement (all fields in GROUP
Hello,
as you all may know, the GROUP BY clause in PostgreSQL has to be parameterized
with all fields that appear in the SELECT clause (except aggregates).
So
SELECT id, foo, sum(bar)
FROM table1
GROUP BY id, foo;
is perfectly valid, where
SELECT id, foo, sum(bar)
FROM table1
GROU
On Tuesday 02 August 2005 19:49, Tom Lane wrote:
> Oliver Siegmar <[EMAIL PROTECTED]> writes:
> > I did a hexdump on the files within the tabelspace directory...no
> > business data at all, only postgres internals (I saw a lot of function
> > names and datatypes).
>
&
On Tuesday 02 August 2005 18:42, Tom Lane wrote:
> > I dropped the database with 'DROP DATABASE xxx;' without any problems
> > (after the tablespace run out of space).
>
> How exactly do you know that OID 595675173 is the database you dropped,
> and not that of some other DB?
I don't know that for
On Tuesday 02 August 2005 17:01, Michael Fuhr wrote:
> Hmmm...based on the file names, it looks like the directory contains
> only system tables. Do you know what database this was?
Yes, a business database - not a system one. The database were created using
template0.
> Did you
> explicitly
On Tuesday 02 August 2005 15:16, Michael Fuhr wrote:
> > This directory indeed contains a subdirectory named 595675173 (the
> > ghost's database oid ;-))
>
> Does that subdirectory contain anything? That's part of why I asked
> for the "ls -alR" output; I was also curious to see if there were
> an
On Monday 01 August 2005 22:15, Michael Fuhr wrote:
> On Mon, Aug 01, 2005 at 09:28:07PM +0200, Oliver Siegmar wrote:
> > template1=# select * from pg_tablespace_databases(594611987);
> > pg_tablespace_databases
> > -
> > 595675173
> > (1
Hello,
I'm unable to drop a recently created tablespace (the partition on which the
tablespace relies on, run out of space - postgresql seems to have a problem,
now):
template1=# drop tablespace disk1;
ERROR: tablespace "disk1" is not empty
Huh? Okay...lets dig into...
template1=# select
Hi all,
just wanted to let you know (maybe you also know :)) - pgsql 7.4 is great!
I had do migrate a mysql database to pgsql within the database -
dump mysql database
restore that dump in pgsql
spread about 30 tables in >160 new tables (new database design)
...this migration took about 3,5 hrs.
