I wrote:
> If I recall the previous discussions correctly there were still some
> gotchas :-(
One point that comes to mind after more thought is that you'd really
like "create table ... default nextval('foo') ..." to understand that
there is a dependency from the column's default expression to seq
Thank you for your responses. I got impatient and tried installing 8.0.2
and had no problems whatsoever. I will follow up on your suggestions if
I get to install 8.0.3.
Thanks again.
On Thu, 2005-09-22 at 11:23 -0400, Tom Lane wrote:
> "Prasad Duggineni" <[EMAIL PROTECTED]> writes:
> > Try turni
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> On Thu, Sep 22, 2005 at 10:29:21PM -0400, Tom Lane wrote:
>> (wanders off, wondering if a "regclass" literal value would help ...)
> Wouldn't it be easy to create a nextval(oid) function, and have SERIAL
> emit that instead?
Well, for one thing, "nextv
On Thu, Sep 22, 2005 at 10:29:21PM -0400, Tom Lane wrote:
> To my mind the appropriate fix is to come up with some arrangement
> that allows the stored form of NEXTVAL(seq) to specify the referenced
> sequence directly (by OID) rather than as a text string. There are some
> speculations about thi
Tom Lane wrote:
> Bruce Momjian writes:
> > This item has been added to the 8.1 bugs list:
> > http://momjian.postgresql.org/cgi-bin/pgbugs
>
> This isn't going to be fixed for 8.1. I think it's really a variant of
> the TODO item
> o %Have ALTER TABLE RENAME rename SERIAL sequence nam
Bruce Momjian writes:
> This item has been added to the 8.1 bugs list:
> http://momjian.postgresql.org/cgi-bin/pgbugs
This isn't going to be fixed for 8.1. I think it's really a variant of
the TODO item
o %Have ALTER TABLE RENAME rename SERIAL sequence names
To my mind the appropr
This item has been added to the 8.1 bugs list:
http://momjian.postgresql.org/cgi-bin/pgbugs
---
Kouber Saparev wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1883
> Logged by:
Douglas Toltzman <[EMAIL PROTECTED]> writes:
> It was my understanding that a NULL value would be not-equal to any
> non-null value. Am I wrong about this?
Yes. A NULL is neither equal nor unequal to anything else.
You can use IS DISTINCT FROM to get the behavior you are looking for,
but it mi
Maybe this is just my misunderstanding of how this should work, but
I've got a table with a char(6) field named member_status. When I
select "member_status != '*'" or "member_status <> '*'", I get 14856
rows. However, if I select "member_status is null or member_status !=
'*'", I get 20308 ro
On Monday 19 September 2005 14:01, Clark, Andrew wrote:
> Hi all,
>
> I've found the when psql is used with the -f flag and the specified file
> doesn't exist the rc value is 0.
>
> $ uname -a
> SunOS bld 5.8 Generic_108528-29 sun4u sparc SUNW,Sun-Fire-V440
>
> $ psql -V
> psql (PostgreSQL) 8.0.2
>
A patch has been applied and this will be fixed in 8.0.4 and 8.1beta3.
---
Robert Treat wrote:
> On Monday 19 September 2005 14:01, Clark, Andrew wrote:
> > Hi all,
> >
> > I've found the when psql is used with the -f flag a
"Brian Cox" <[EMAIL PROTECTED]> writes:
> any_db=> create view view1 as select null as col1 from any_table;
> CREATE VIEW
You seem to have ignored the warning telling you this probably wasn't
a good idea:
regression=# create view view1 as select null as col1;
WARNING: column "col1" has type "unk
"Prasad Duggineni" <[EMAIL PROTECTED]> writes:
> Try turning the enforcement mode off.
Or put the data directory where the standard selinux policy expects it
to be, namely /var/lib/pgsql/data.
The lack of any useful error message is a selinux policy bug, which
appears to be fixed in reasonably-c
Try turning the enforcement mode off.
- Original Message -
From: "SriKumar Kareti" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, September 21, 2005 2:49 PM
Subject: [BUGS] possible bug...
Hello!
I am trying to install postgres 8.0.3 from rpms.
[EMAIL PROTECTED] ~]$ rpm -qa | grep postg
On Wed, Sep 21, 2005 at 01:49:35PM -0500, SriKumar Kareti wrote:
Hi,
> creating directory /usr/local/pgsql/data/base/1 ... ok
> creating directory /usr/local/pgsql/data/pg_tblspc ... ok
> selecting default max_connections ... 10
> selecting default shared_buffers ... 50
> creating configuration f
The following bug has been logged online:
Bug reference: 1904
Logged by: Brian Cox
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Linux (Fedora Core 2)
Description:using distinct with null col causes error
Details:
any_db=> create view
Hello!
I am trying to install postgres 8.0.3 from rpms.
[EMAIL PROTECTED] ~]$ rpm -qa | grep postgres
postgresql-8.0.3-1PGDG
postgresql-server-8.0.3-1PGDG
postgresql-libs-8.0.3-1PGDG
[EMAIL PROTECTED] ~]$
After I install the RPMs, when I try to initdb I run into problems.
I did set the data dir
17 matches
Mail list logo
