I am a new user to PG (graduating from Access) and had some problems with
inheritance. I stumbled into the inheritance to-do discussion and would like
to put in my two cents. I apologize if this is not the right place to be
sending this.
It seems PG needs two separate types of inheritance: struc
Hi there,
recently I tried the following using my psql-client:
select version();
version
---
PostgreSQL 7.1.2 on i686-pc-linux-gnu, compiled by GCC 2.95.2
(1 row)
create tabl
Great, thanks for letting me know Bruce.
Regards, Dave.
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]]
> Sent: 12 October 2001 18:54
> To: Dave Page
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: [BUGS] Possible bug in ALTER TABLE RENAME COLUMN
> (PostgreSQL 7.1.3)
>
Hey all,
I have just been installing v7.1.3 on Linux Sparc -
all build and make went well.
However, initdb reports "mkdir: cannot create
directoy /usr/local/pgsql/data': No space left on device.
initdb failed.
Permissions on /usr/local/pgsql/data, with owner
postgres:daemon, allow rwx.
On Wed, 10 Oct 2001, Ralf Miller wrote:
> First question:
> The example shows that the column number of type serial is incremented
> as if the preceding insert-statement was successfull, even if it was
> not.
> Are the values for the column number of type serial inserted into the
> corresponding
Sherwin Daganato ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
psql (7.1.3) doesn't like sysid=0
Long Description
I have migrated a production database from 7.0.3
to 7.1.3 successfully. Then I was trying to load this
databas
bipin ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
could not copy dump files to postgres directory
Long Description
i could not copy the dump file of a database into the postgres directory.when i try to
login to postgresuse
Hi.
System Configuration
-
Architecture: Intel Pentium
Operating System: FreeBSD 4.2-STABLE
PostgreSQL version: PostgreSQL-7.1.2
Compiler used: gcc 2.95.2
Description of problem
--
Some data-tables accumulate infromation from the system
Ralf Miller <[EMAIL PROTECTED]> writes:
> The example shows that the column number of type serial is incremented
> as if the preceding insert-statement was successfull, even if it was
> not.
This is intentional. Sequence nextval() operations do not roll back.
> The SEQUENCE corresponding to a c
Something strange is going on. Postgres keeps wanting to do a sequential
scan of my table when it REALLY should be using it's indexes.
I am running postgresql-7.1.3-1PGDG on RedHat 6.2 and on RedHat 7.0.
I have 300,000 records in this table and yes, I have vacuum analyzed.
Here is my table:
Hi.
Are you sure it's for me ?
In the bugreport said about mysql2pgsql, however I'm the author of my2pg.pl.
Both tools are distributed with Postgres source distribution.
Please confirm that's really for me.
Thanks.
Max Rudensky.
On Wed, 10 Oct 2001 15:45:22 -0400 (EDT)
Bruce Momjian <[EMAIL PRO
Ralf Miller writes:
> The example shows that the column number of type serial is incremented
> as if the preceding insert-statement was successfull, even if it was
> not.
The serial type does not provide consecutive numbers, only unique ones.
> The SEQUENCE corresponding to a column of type ser
I posted two things I thought might be bugs about an hour ago with
postgresql-7.1.3-1PGDG. I just ran a regression test with postgresql-7.0.3
and one problem vanished and one stayed.
(yes I vacuum analyzed)
1) the
select * from foo where text_field like 'foo%'
will do an index sc
13 matches
Mail list logo
