The following bug has been logged online:
Bug reference: 2070
Logged by: Jan Jockusch
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: Linux
Description:Encoding dependent error in comparison operators
Details:
With terminal encoding Lati
The following bug has been logged online:
Bug reference: 2069
Logged by: Hubert FONGARNAND
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Linux
Description:Cursors are not close outside of a function
Details:
I've written a little test fu
The following bug has been logged online:
Bug reference: 2071
Logged by: Prakash Nair
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.4
Operating system: RHES
Description:ERROR: invalid multibyte character for locale
Details:
Hello,
Got the error in postg
"Jan Jockusch" <[EMAIL PROTECTED]> writes:
> With terminal encoding Latin-1, client encoding Latin-1
> and database encoding LATIN1, I do:
... and what database locale? This sort of misbehavior is a common
symptom of having a database encoding that's not what the locale
expects.
"Hubert FONGARNAND" <[EMAIL PROTECTED]> writes:
> Note that i don't close c1 after returning...
> (c1 should be close automatically because it is declared inside my
> function);
What makes you think that?
If we forcibly closed cursors at function exit, it'd be impossible to
return a cursor refere
On 11/24/05, Hubert FONGARNAND <[EMAIL PROTECTED]> wrote:
> Note that i don't close c1 after returning...
> (c1 should be close automatically because it is declared inside my
> function);
>
From the manual (signs are mine)...
35.8.3.3. Returning Cursors
PL/pgSQL functions can return cursors to th
Simon Riggs wrote:
> On Fri, 2005-11-18 at 09:32 -0500, Tom Lane wrote:
> > All known CVE problems are resolved in 8.0.4.
>
> I was unaware of this. I've looked at the release notes and searched the
> archives, but this doesn't seem to be mentioned by CVE number. (The
> vulnerabilities and their
Bruce Momjian wrote:
> I am not excited about referencing error numbers from someone else.
> We know our errors better than anyone else, so I don't see the point.
The point is, *we* might know our error numbers, but the rest of the
world doesn't.
And CVE isn't just "someone". A large number of
On Fri, 2005-11-25 at 12:20 -0500, Bruce Momjian wrote:
> Simon Riggs wrote:
> > On Fri, 2005-11-18 at 09:32 -0500, Tom Lane wrote:
> > > All known CVE problems are resolved in 8.0.4.
> >
> > It seems like we need a much clearer resource for security admins to
> > check our compliance levels. Thi
Simon Riggs <[EMAIL PROTECTED]> writes:
> Unless somebody else wants to do this, I'll discuss on -www how we can
> get a page up on the .org site with this info on, so that we can be "CVE
> compatible".
IMHO we should do that in any case, whether or not we mention CVEs
in our release notes or CVS
If someone wants to create a separate web page to track fixes related to
CVE number, that is fine. My guess is that most people reading the
release notes don't care about the CVE numbers themselves (just that
each release has all known security bugs fixed), and most bugs that are
fixed don't have
Tom Lane wrote:
> "Wim Audenaert" <[EMAIL PROTECTED]> writes:
> > When I create a new database, this function (oid 17039 and used for utf8
> > translation) is not defined in the pg_proc table. I tried to create a new
> > database. The pg_proc table contains several functions, but not this one.
>
Bruce Momjian wrote:
If someone wants to create a separate web page to track fixes related to
CVE number, that is fine. My guess is that most people reading the
release notes don't care about the CVE numbers themselves (just that
each release has all known security bugs fixed), and most bugs tha
John R Pierce wrote:
> Bruce Momjian wrote:
> > If someone wants to create a separate web page to track fixes related to
> > CVE number, that is fine. My guess is that most people reading the
> > release notes don't care about the CVE numbers themselves (just that
> > each release has all known se
On Fri, Nov 25, 2005 at 11:55:44AM +, Prakash Nair wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2071
> Logged by: Prakash Nair
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.4
> Operating system: RHES
> Description:ERROR:
15 matches
Mail list logo
