The following bug has been logged online:
Bug reference: 4005
Logged by: felix wildung
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.03
Operating system: NFTS
Description:installation error
Details:
When I try to creat my user account the installation abort
> > commit 69db64c737012a8d2d6fbcce3ace7136cb2bc85f
> > Author: branch-fixup
> > Date: Wed Feb 13 03:40:38 2008 +
>
> > Removing files not present on branch REL8_3_STABLE:
> > configure
> > configure.in
> > doc/bug.template
> > src/include/pg_config.h.win
felix wildung wrote:
The following bug has been logged online:
Bug reference: 4005
Logged by: felix wildung
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.03
Operating system: NFTS
Description:installation error
Details:
When I try to creat my user account
Michael Meskes wrote:
I just committed the attached small fix to CVS HEAD and the 8.3 branch.
This should fix your problem.
Michael
diff --exclude CVS -ru /home/postgres/pgsql-ecpg/preproc/type.c preproc/type.c
--- /hom
The following bug has been logged online:
Bug reference: 4006
Logged by: David Schweikert
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: Linux
Description:pg_ctl assumes that all config files lie in
data_directory
Details:
pg_ctl doesn'
Michael Meskes wrote:
On Sat, Mar 01, 2008 at 04:50:46PM -0300, Euler Taveira de Oliveira wrote:
ecpg_test.pgc:36: error: invalid application of `sizeof' to incomplete type
`varchar_h_tunnel_active'
It seems that are you using implicit cast from varchar to inet. It
doesn't work in 8.3 anymo
The following bug has been logged online:
Bug reference: 4007
Logged by: Steve Clark
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: FreeBSD 6.2
Description:chr(0) doesn't work anymore
Details:
Until 8.3.0 the following worked:
SELECT co
"Steve Clark" <[EMAIL PROTECTED]> writes:
> Until 8.3.0 the following worked:
> SELECT coalesce(param_value,chr(0)) from t_system_params where param_name =
> 'default_unit_key';
It would have "worked" only for rather small values of "work", since
most of the support for type TEXT isn't null-safe.
"David Schweikert" <[EMAIL PROTECTED]> writes:
> pg_ctl doesn't work if you put postgresql.conf in a different directory than
> the database data files.
Yeah, this is a known limitation that seems unlikely to get fixed soon,
as doing it right would appear to require giving pg_ctl the ability to
pa
Steve Clark <[EMAIL PROTECTED]> writes:
> I'm not sure I understand what you mean about TEXT being null-safe.
> What are the issues, and why was
> it supported for years and now abruptly changed.
It never was supported, we are simply plugging a hole that let you
create a text value that would be
Tom Lane wrote:
"Steve Clark" <[EMAIL PROTECTED]> writes:
Until 8.3.0 the following worked:
SELECT coalesce(param_value,chr(0)) from t_system_params where param_name =
'default_unit_key';
It would have "worked" only for rather small values of "work", since
most of the support for type TEXT
Tom Lane wrote:
> "David Schweikert" <[EMAIL PROTECTED]> writes:
> > pg_ctl doesn't work if you put postgresql.conf in a different directory than
> > the database data files.
>
> Yeah, this is a known limitation that seems unlikely to get fixed soon,
> as doing it right would appear to require giv
On Wed, Feb 20, 2008 at 3:55 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Alex Hunsaker" <[EMAIL PROTECTED]> writes:
> > create table junk (val integer not null, val2 integer);
> > create table junk_child () inherits (junk_1);
> > alter table junk_child alter column val drop not null;
> > insert
Hi,
On Mon, Mar 03, 2008 at 12:12:16 -0500, Bruce Momjian wrote:
> pg_ctl can not read the pid file because it isn't located in the
> config directory but in the PGDATA directory. The solution is to
> allow pg_ctl to read and understand postgresql.conf to find the
> data_directory value.
The following bug has been logged online:
Bug reference: 4008
Logged by: Robert Fritzsching
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3, 8.3.0
Operating system: Windows XP, Linux Debian SID
Description:accepts invalid input with domaintypes and outer jo
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
---
Ma
"Robert Fritzsching" <[EMAIL PROTECTED]> writes:
> If I insert data in a table with left outer join, I get no error even though
> the domain type should trigger an error.
This has been discussed before. Most of us think it's a bug in the SQL
spec that the issue even exists. What would you expect
"Alex Hunsaker" <[EMAIL PROTECTED]> writes:
> On Wed, Feb 20, 2008 at 3:55 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>> Actually the bug is that ALTER TABLE allows you to do that. It should
>> not be possible to drop an inherited constraint, but right now there's
>> not enough information in the sys
Has this been addressed?
---
Mike Leahy wrote:
>
> The following bug has been logged online:
>
> Bug reference: 3983
> Logged by: Mike Leahy
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.3.0
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
---
Ma
20 matches
Mail list logo
