On Wed, Nov 17, 2004 at 02:49:15PM +1100, John Hansen wrote:
> The following function:
[snip]
> creashes the backend, UNLESS it's executed in the same session where it was
> created.
I can reproduce this crash on the following platform:
Solaris 9
PostgreSQL 8.0.0beta4 (CVS)
Perl 5.8.5
g
Andrew - Supernews <[EMAIL PROTECTED]> writes:
> On 2004-11-16, Tom Lane <[EMAIL PROTECTED]> wrote:
>> [ thinks ... ] OK, so the problem case is where perl was built with a
>> different compiler than we're building PG with,
> Which is a non-starter in any event - you can't reliably embed perl int
Jeffrey Melloy <[EMAIL PROTECTED]> writes:
> I've run across a bug with order by:
> select 1 as a order by a;
> -- works
> select 1 as a, 2 as b order by a + b;
> ERROR: column "a" does not exist
This isn't a bug, strangely enough. The "order by output-column-name"
syntax is a holdover from SQL
On Tue, 2004-11-16 at 21:13 +0100, Magnus Hagander wrote:
> Upon reviewing this patch, I notice this horrible line slipped into the
> patch earlier up (in the #ifdef WIN32 section):
> + printf("uhh\n");fflush(stdout);
>
> Oopsie. Could you remove that, or do you want a patch to do it?
On Tuesday 16 November 2004 21:06, Tom Lane wrote:
> Stefanos Harhalakis <[EMAIL PROTECTED]> writes:
> > I believe that the checks in src/backend/libpq/be-secure.c:653 should be
> > performed in a different order (first the access permissions and then the
> > owner of the key) just to give a more a
The following function:
create function text_to_words(text)
returns setof text as $_$
my %stopwords = ( 'i' => 'i','me' => 'me','my' => 'my','myself' =>
'myself','we' => 'we','our' => 'our','ours' => 'ours','ourselves' =>
'ourselves','you' => 'you','your' => 'your','yours' => 'yours','yourse
On 2004.11.16 16:25 Tom Lane wrote:
"Karl O. Pinc" <[EMAIL PROTECTED]> writes:
> I deleted the 'public' schema from my databases
> in 7.3, now in 7.4 they are back.
IMHO this is not a bug. It is not pg_dump's charter to remove
system-created objects...
I can live with this, but I find the implicat
Hi,
I am using PostgreSQL 8.0.0 Beta 4. I have an application written on
C++ Builder (connets through ADO). I
found that sometimes the connections breaks when the application has an open
connection and when I connect to the same server with „pgAdmin III“...
Maybe it‘s „pgAdmi
I've run across a bug with order by:
select 1 as a order by a;
-- works
select 1 as a, 2 as b order by a;
-- works
select 1 as a, 2 as b order by a + b;
ERROR: column "a" does not exist
select * from (select 1 as a, 2 as b) stuff order by a + b;
-- works
---(end of broadcast
On 2004-11-16, Tom Lane <[EMAIL PROTECTED]> wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
>> The ldopts value contains compiler-specific shared library linking flags
>> plus information about additional library to link in. The ccdlflags
>> value contains only the compiler-specific shared
"T.J." <[EMAIL PROTECTED]> writes:
> To clarify, what I have experienced was in all versions of 8.0.0.beta,
> it did not just happen between 3 to 4. It was the change from 7.4 to
> 8.0. The error was not just windows based as I built psql on a seperate
> linux machine communicating with a linux
To clarify, what I have experienced was in all versions of 8.0.0.beta,
it did not just happen between 3 to 4. It was the change from 7.4 to
8.0. The error was not just windows based as I built psql on a seperate
linux machine communicating with a linux server and got the same
results. I created
"Karl O. Pinc" <[EMAIL PROTECTED]> writes:
> It appears as though pg_dumpall is setting the search_path
> runtime variable in the databases before it creates the
> schemas. Further, it appears as though the ALTER
> DATABASE command used to set the search path does
> not have the quotes correct.
T
Tom Lane wrote:
> Peter, it was you that committed the current contents of
> config/perl.m4; do you recall why it wants to remove ccdlflags from
> the Embed results?
The ldopts value contains compiler-specific shared library linking flags
plus information about additional library to link in. The
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> The ldopts value contains compiler-specific shared library linking flags
> plus information about additional library to link in. The ccdlflags
> value contains only the compiler-specific shared library linking flags.
> If we subtract the second fr
Hi Magnus,
I had the same problem, and your answer helped me to get PostGreSQL
finally installed by removing the existing LIBEAY32.DLL.
As far as I could find out, my LIBEAY32.DLL had been installed by
CrystalReports 10 and it has the version number 0.9.6.101, a size of
657 KB and the date of th
On 2004-11-16, Tom Lane <[EMAIL PROTECTED]> wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
>> As I originally said in IRC, I do not know why the configure script is
>> trying to second-guess the ExtUtils::Embed output; however, what it is
>> doing clearly produces the wrong results.
>
> I'
"Karl O. Pinc" <[EMAIL PROTECTED]> writes:
> I deleted the 'public' schema from my databases
> in 7.3, now in 7.4 they are back.
IMHO this is not a bug. It is not pg_dump's charter to remove
system-created objects...
regards, tom lane
---(end of b
Dear Sir/Madam:
I encounter some error while trying to build postgresql-8.0.0beta4.
When I run gmake, it reports that some macros used in path.c are not defined.
I check that file and find that macros such as PGBINDIR are really not
defined.
Please tell me what should I do now.
Thanks.
-Original Message-
From: "Magnus Hagander" <[EMAIL PROTECTED]>
To: Kristian Jörg <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
Date: Sun, 14 Nov 2004 14:12:07 +0100
Subject: RE: [BUGS] PostgresQL 8 beta 4 bugs
> >Hello, I have found two bugs relating to the Windows port, i.e
> >installing on
This one gave me grief also.
The fix turns out to be pretty simple.
libeay32.dll is located in System32 and can be installed by any number of
applications, maybe the most notable being Crystal Reports.
More than likely the version on your machine is not recent enough to have
the required ent
Hi,
Went to upgrade from postgresql (RedHat's postgresql
rh-postgresql-7.3.6-7) to Fedora core 3 postgresql
7.4.6-1 and encountered a problem. If nothing else this
is worth a note on the 7.4 upgrade doc page.
It appears as though pg_dumpall is setting the search_path
runtime variable in the databa
Hi,
Went to upgrade from postgresql (RedHat's postgresql
rh-postgresql-7.3.6-7) to Fedora core 3 postgresql
7.4.6-1 and encountered a problem. If nothing else this
is worth a note on the 7.4 upgrade doc page.
I deleted the 'public' schema from my databases
in 7.3, now in 7.4 they are back. I supp
On Tue, 2004-11-16 at 12:34, Devrim GUNDUZ wrote:
> > Description:7.3.8 server RPM has file error
> >
> > Details:
> >
> > Installing postgresql-server-7.3.8-2PGDG.i686.rpm,
> > I get the following error:
> > error: unpacking of archive failed on file
> > /usr/lib/pgsql/utf8_and_gb18030.so;
Andrew - Supernews <[EMAIL PROTECTED]> writes:
> On 2004-11-16, Tom Lane <[EMAIL PROTECTED]> wrote:
>> Don't you think this is likely to break more cases than it fixes?
> You're not correctly understanding what it does.
Doh. You're right, I misread the (unnecessarily obscure) sed command.
> As
On 2004-11-16, Tom Lane <[EMAIL PROTECTED]> wrote:
> David Walker <[EMAIL PROTECTED]> writes:
>> This patch to postgresql-7.4.6/config/perl.m4 fixes the problem:
(The patch in question is based on suggestions of mine made in IRC, so I'll
comment on the technical details)
> Don't you think this is
On Tue, Nov 16, 2004 at 03:33:49PM -0500, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > Sounds like a problem due to the backend in recent betas demanding
> > a client certificate if $PGDATA/root.crt exists, but the client
> > certificate doesn't exist in ~/.postgresql/postgresql.{
Michael Fuhr <[EMAIL PROTECTED]> writes:
> Sounds like a problem due to the backend in recent betas demanding
> a client certificate if $PGDATA/root.crt exists, but the client
> certificate doesn't exist in ~/.postgresql/postgresql.{crt,key}.
If that is the problem, it's still broken because the e
On Tue, Nov 16, 2004 at 03:01:23PM -0500, Tom Lane wrote:
> "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> > After installing 8.0.0beta4 (previously tried with beta3,2,etc) on a linux
> > system with a working 7.4.x installation I was unable to connect with ssl.
> > Tried compiling with Ope
>> After installing 8.0.0beta4 (previously tried with
>beta3,2,etc) on a linux
>> system with a working 7.4.x installation I was unable to
>connect with ssl.
>> Tried compiling with OpenSSL 0.9.7d/e. I used certificates
>created with
>> OpenSSL 0.9.7d/e that both worked fine with 7.4.x but
>
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> After installing 8.0.0beta4 (previously tried with beta3,2,etc) on a linux
> system with a working 7.4.x installation I was unable to connect with ssl.
> Tried compiling with OpenSSL 0.9.7d/e. I used certificates created with
> OpenSSL 0.9.7d/
David Walker <[EMAIL PROTECTED]> writes:
> This patch to postgresql-7.4.6/config/perl.m4 fixes the problem:
Don't you think this is likely to break more cases than it fixes?
You can't just arbitrarily say that no one else is going to need
the ccdlflags.
On the two platforms I checked it on, it se
Stefanos Harhalakis <[EMAIL PROTECTED]> writes:
> I believe that the checks in src/backend/libpq/be-secure.c:653 should be
> performed in a different order (first the access permissions and then the
> owner of the key) just to give a more appropriate message.
Changing the order of the tests wouldn
Your name : David Walker
Your email address : [EMAIL PROTECTED]
System Configuration
-
Architecture (example: Intel Pentium): Intel PII(Linux) and Intel
PPro(FBSD)
Operating System (example: Linux 2.4.18) : Linux 2.6.9 & FreeBSD
4.10-RELEASE-p3
Hi there,
PostgreSQL 7.4.6 gives the following error message when trying to read the
private key in the case of:
-rw--- 1 root root 887 Aug 19 15:01 /var/lib/postgres/data/server.key
2004-11-13 13:04:42 [4095] FATAL: unsafe permissions on private key file
"/var/lib/postgres/data/server.k
"John Kennedy" <[EMAIL PROTECTED]> writes:
> I am very new to PostgreSQL so apologies in advance if this bug report is a
> waste of time for some reason.
Not at all. Looks like you've found a mistake in where variables of
pass-by-reference datatypes get stored. Thanks for the report!
The following bug has been logged online:
Bug reference: 1323
Logged by: Sandro Votre
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 Beta
Operating system: Windows NT, Windows XP
Description:Bug in Driver ODBC
Details:
I work with Delphi language , ..
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> Description:Bug while Insert into TempResult Select cols .
> statement
It is not possible to investigate this report based on the small amount of
information you provided. Give us a test case, or at least something
that would give
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Simon,
On Tue, 16 Nov 2004, PostgreSQL Bugs List wrote:
Description:7.3.8 server RPM has file error
Details:
Installing postgresql-server-7.3.8-2PGDG.i686.rpm,
I get the following error:
error: unpacking of archive failed on file
/usr/lib/pg
The following bug has been logged online:
Bug reference: 1322
Logged by: Bahadur Singh
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 Beta
Operating system: Windows 2000 server
Description:Bug while Insert into TempResult Select cols .
statement
D
Greetings.
I am very new to PostgreSQL so apologies in advance if this bug report is a
waste of time for some reason.
Summary:
I have been experimenting with 8.0 Beta4 on Windows XP and the attached SQL
resulted in a crash of the database (not the postmaster as far as I can
tell). My code creat
41 matches
Mail list logo
