The following bug has been logged online:
Bug reference: 3660
Logged by: Thomas Reiss
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3 beta 1
Operating system: Linux
Description:unused empty file is created with csvlog
Details:
Hello,
I just tried the csvlo
"Thomas Reiss" <[EMAIL PROTECTED]> writes:
> I set the following :
> log_destination = 'csvlog'
> logging_collector = on
> log_filename = 'postgresql-%u'
> At server start, PostgreSQL creates a file called "postgresql-2" (for today)
> and a file "postgresql-2.csv".
This is not a bug.
> File "po
Hello,
first, congratulations for 8.3beta1. I built some initial
Debian/Ubuntu packages which went very smoothly.
I am now walking through the failures of my postgresql-common test
suite. One particular regression is that there seems to be no way any
more to inhibit the password prompt in psql.
Hi again,
Martin Pitt [2007-10-09 15:56 +0200]:
> (2) PGPASSFILE=/dev/null psql -l
>
>With /dev/null I get a segfault (I'll probably send a patch for
>that later).
Ah, it tried to free(pgpassfile) in PasswordFromFile(), but that is a
local stack variable.
Can you please apply this upstr
On Tue, Oct 09, 2007 at 04:32:02PM +0200, Martin Pitt wrote:
> Hi again,
>
> Martin Pitt [2007-10-09 15:56 +0200]:
> > (2) PGPASSFILE=/dev/null psql -l
> >
> >With /dev/null I get a segfault (I'll probably send a patch for
> >that later).
>
> Ah, it tried to free(pgpassfile) in PasswordF
I'm not entirely sure if this is a bug. Basically I have a python
function that needs to create new functions. I intended on doing this
through the plpy.excute("create function...")
Unfortunately this crashes postmaster v8.0.3. I'm kind of bound to
this version - but it would be good to know if so
The following bug has been logged online:
Bug reference: 3661
Logged by: David Bachmann
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3-beta1
Operating system: Windows XP
Description:Missing equality comparator: string = integer
Details:
This does not funct
The following bug has been logged online:
Bug reference: 3662
Logged by: Robins Tharakan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5
Operating system: Windows XP Professional SP2
Description:Seems that more than one run of a functions causes an
error
De
The following bug has been logged online:
Bug reference: 3663
Logged by: Kevin.Lee
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3-beta1
Operating system: Windows XP JP
Description:Installer: Encoding(Server) Select list have not UTF-8
encoding.
Details:
Wh
Hi.
Yes, you look at the same thing as this.
http://winpg.jp/~saito/pginstaller/pginstaller_8.3.beta1-error1.png
I will correct it after discussion. Thanks!
Regrad,
Hiroshi Saito
- Original Message -
From: "Kevin.Lee" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, October 10, 2007 1:05 A
Am Dienstag, 9. Oktober 2007 schrieb David Bachmann:
> This does not function any more under PG 8.3-beta1:
>
> select '5'::varchar = 5;
> ERROR: operator does not exist: character varying = integer
That is intentional. Fix your application by inserting appropriate explicit
casts.
--
Peter Eis
>
> This does not function any more under PG 8.3-beta1:
>
> select '5'::varchar = 5;
> ERROR: operator does not exist: character varying = integer
>
> select '5'::char = 5;
> ERROR: operator does not exist: character = integer
you cannot compare any character type and numeric type. If you wont t
Hi,
I submitted this (supposed bug) via a web form earlier, but it got back with
this bounce.
Since I was not sure whether this was accepted, so I registered with this
list and am sending this again.
Hope it helps to find the problem.
Robins
-- Forwarded message --
From: [EMAIL
Kevin.Lee wrote:
> The following bug has been logged online:
>
> Bug reference: 3663
> Logged by: Kevin.Lee
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.3-beta1
> Operating system: Windows XP JP
> Description:Installer: Encoding(Server) Select list have n
The following bug has been logged online:
Bug reference: 3664
Logged by: Maciej Szarlinski
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5
Operating system: Windows XP SP 2
Description:CANNOT LOAD FROM FILE
Details:
Problem appears when I try to load a co
"blay bloo" <[EMAIL PROTECTED]> writes:
> Unfortunately this crashes postmaster v8.0.3.
> ...
> /usr/lib/libpython2.5.so.1.0(PyEval_EvalFrameEx+0x165c)[0x61d5f6c]
I think the short answer is that PG 8.0.x doesn't support python 2.5,
period. Why do you feel that you must use a hoary PG version but
Martin Pitt wrote:
> For example, "psql -l" is a convenient
> method to check whether the postmaster is running at all,
> finished with startup and ready for connections.
>
Why not just "pg_ctl status"?
--
Euler Taveira de Oliveira
http://www.timbira.com/
---(end o
17 matches
Mail list logo
