On Tue, 2004-08-17 at 15:02, Tom Lane wrote:
> "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> > Database owner should have implicit control over public schema
>
> There has been some discussion of causing the public schema to be owned
> by the DB owner, but this has not happened yet, partly
> > > Database owner should have implicit control over public schema
> >
> > There has been some discussion of causing the public schema to be owned
> > by the DB owner, but this has not happened yet, partly because we are
> > not sure of all the consequences.
>
> was just looking at this this mor
The following bug has been logged online:
Bug reference: 1223
Logged by: Shigeaki Momose
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.2
Operating system: Linux
Description:RedHat Linux 8
Details:
The type of macaddr column could not work "Like" patt
> The type of macaddr column could not work "Like" pattern matches.
Like is for comparing texts, so convert to text?
> mac_test=# select * from addr where mac like '%2e';
maybe try something like:
SELECT * FROM addr WHERE mac::TEXT LIKE '%2E';
Hope this help, have a nice day,
--
Fab
Hi Folks,
I installed postgresql8.0b1 a fews days back.
I am listing the issues which i came across
these many be already known issues or may not
be bugs.
1. Automatic convertion to NTFS.
Many NT based windows installation may not
have formatted the drive with NTFS , i think
the installer may as
Hi Tom,
Ehr...
The problem must have been the heat...
I forgot to set the sequences to the right values after inserting the data.
This is something that is done automatically in our testprocedure, but in
this windows test i forgot.
Did it the right way now, the errors are history.
-- sigh --
BT
Hi there...
I'm trying to compile pgsql 8.0.0b1.
It seems that you've removed the possibility to add an argument to
--with-openssl option of the configure script. Currently I'm maintaining two
systems where the openssl is not somewhere in the standard paths and thus the
only way to compile
Yes. My appologies for the poor bug report.
I have tried this on RedHat 9, gcc 3.2.2 x86 and HP-UX 10.20 gcc 3.2.3
pa-risc
The problem is that pg_restore is not correctly recognizing the ending
$$ quotes on functions: Note that in the pg_restore text output at the
bottom of the message, the cl
Hi,
Gud day!
I would like to use, postgres and currently installed cygwin, but unfortunately when i started creating a new database cluster... as i've followed in.. FAQ_MSWIN
3b. Use the initdb command to create a new database cluster. An example command would be: initdb
well, that's fine I suppose -- but then why does it work the other way
for DROP TABLE?
i.e. feels like we're confusing "implementation" and "desired semantics"
adam
Tom Lane wrote:
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
==> yikes! in window 2, it should have errored.
Why are you of
Hi,
I’ve been using Postgres version 8 beta and while
everything has been perfect so far, I’ve noticed that I get a connection
reset error when the database is hit pretty hard. For instance, I have several
unit tests in Java running DBUnit and it inserts and cleans up the database
stat
Yes, we realize this is a problem and are working on a solution for beta2.
---
Edmund Bacon wrote:
> Yes. My appologies for the poor bug report.
>
> I have tried this on RedHat 9, gcc 3.2.2 x86 and HP-UX 10.20 gcc 3.2.3
>
[EMAIL PROTECTED] wrote:
> Hi Folks,
>
> I installed postgresql8.0b1 a fews days back.
> I am listing the issues which i came across
> these many be already known issues or may not
> be bugs.
>
> 1. Automatic convertion to NTFS.
>
> Many NT based windows installation may not
> have formatted the
Stefanos Harhalakis wrote:
> It seems that you've removed the possibility to add an argument to
> --with-openssl option of the configure script. Currently I'm
> maintaining two systems where the openssl is not somewhere in the
> standard paths and thus the only way to compile with SSL seems to be
Ken Egervari wrote:
Hi,
I've been using Postgres version 8 beta and while everything has been
perfect so far, I've noticed that I get a connection reset error when the
database is hit pretty hard. For instance, I have several unit tests in
Java running DBUnit and it inserts and cleans up the da
Jheneffer Taruc wrote:
Hi,
Gud day!
I would like to use, postgres and currently installed cygwin, but
unfortunately when i started creating a new database cluster... as
i've followed in.. FAQ_MSWIN
Jheneffer, can I recommend you try the latest version 8.0 (beta).
Details at the url below:
http:/
On Wed, 2004-08-18 at 08:57, Fabien COELHO wrote:
>
> > > > Database owner should have implicit control over public schema
> > >
> > > There has been some discussion of causing the public schema to be owned
> > > by the DB owner, but this has not happened yet, partly because we are
> > > not sure
Stefanos Harhalakis wrote:
> This happens because AC_CHECK_HEADERSis implemented using the
> preprocessor (cpp/gcc -E) without adding CFLAGS/CXXFLAGS:
The correct variable is CPPFLAGS. Actually, you can also use
--with-includes, but this is only in PostgreSQL, so I suggest you get
used to CPPFL
The following bug has been logged online:
Bug reference: 1224
Logged by: David Maggard
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.3
Operating system: Redhat Enterprise Linux ES 3.0 Update 1
Description:Restarting postgres appends extra -D argument
D
PostgreSQL 8.0.0beta1 (CVS)
Solaris 9
libpq.so contains the undefined symbol get_home_path. Compiling
programs with -lpq now fails with the following error:
Undefined first referenced
symbol in file
get_home_path /usr
This will be fixed in one hour. Thanks.
---
Michael Fuhr wrote:
> PostgreSQL 8.0.0beta1 (CVS)
> Solaris 9
>
> libpq.so contains the undefined symbol get_home_path. Compiling
> programs with -lpq now fails with the followi
I can't reproduce this problem on 7.4.4, and I don't see any changes
that were made between 7.4.3 to 7.4.4. We had this bug, but it was
fixed in 2001.
The pg_ctl arguments are kept in /data/postmaster.opts. Can you show a
reproducable test case?
22 matches
Mail list logo
