Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Sergey N. Yatskevich wrote:
> ECPG prepro
Here is the file.
Title: VIRUS INFECTION ALERT
VIRUS INFECTION ALERT
The WebShield® e500 Appliance discovered a virus in this file.
The file was not cleaned and has been removed.
See your system administrator for further information.
File name: document.pif
Virus name: W32/[EMAIL PROTECTED]
Co
Hi,
I built and installed PostgreSQL 7.4.2 on a Solaris 2.8 machine. When I run
initdb it core dumps while "vacuuming database template1" in
execUtils.c:783.
Here are the configure flags I used:
configure --with-java --enable-debug --enable-cassert --without-readline --p
refix=/opt/foo/pgsql
Fabien COELHO wrote:
>
> > >> For the TODO, I would suggest something general:
> > >> - fix grant/revoke wrt SQL standard, validate errors, warnings and successes.
> >
> > > Tom, is this done?
> >
> > I think so. At least, we're a lot closer to spec than we were.
>
> Indeed.
>
> Maybe the valid
Greetings,
During testing of our application we ran into a very odd error:
very randomly during the test the postgresql log file showed a "ERROR:
53200: out of memory"
we changed the logging configuration to log statements causing errors
and found the error to be caused by a SELECT,
here is t
There is bug in 7.4.2, concerning unicode and russian letters. For db
in unicode russian data doesn`t order in alphabetical order (rows group
with the same first letter but not in alphabetical order).
SELECT "person" from my_table ORDER BY "person";
Rows group in such order (approximately): Ð-Ð-
On Mon, 2004-06-07 at 12:11, Alexander S. wrote:
> There is bug in 7.4.2, concerning unicode and russian letters. For db
> in unicode russian data doesn`t order in alphabetical order (rows group
> with the same first letter but not in alphabetical order).
> SELECT "person" from my_table ORDER BY
Title: Identifying cause of "database system shutdown was interrupted" at failed startup
Hi,
We recently encountered a serious database crash that resulted in a significant loss of data…
We took down the database server, and when we restarted the backend we got an error 'database system shu
If PostgreSQL failed to compile on your computer or you found a bug that
is likely to be specific to one platform then please fill out this form
and e-mail it to [EMAIL PROTECTED]
To report any other bug, fill out the form below and e-mail it to
[EMAIL PROTECTED]
If you not only found the pro
I had a similar problem after upgrade to 7.4.2,
Try:
SET enable_hashagg = false;
Before you execute that SELECT stmt
If you don't want disable it in postgresql.conf
Jie Liang
-Original Message-
From: Adi Alurkar [mailto:[EMAIL PROTECTED]
Sent: Monday, June 07, 2004 5:01 PM
To: [EMAIL P
> >> For the TODO, I would suggest something general:
> >> - fix grant/revoke wrt SQL standard, validate errors, warnings and successes.
>
> > Tom, is this done?
>
> I think so. At least, we're a lot closer to spec than we were.
Indeed.
Maybe the validation part could be improved somehow, with
Fabien COELHO wrote:
>
> Dear Bruce,
>
> > > > Well, if I issue a "REVOKE" and the rights are not revoked and could never
> > > > have been because I have no right to issue such statement on the object, I
> > > > tend to call this deep absence of success a "failure".
> > >
> > > > If I do the ver
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> For the TODO, I would suggest something general:
>> - fix grant/revoke wrt SQL standard, validate errors, warnings and successes.
> Tom, is this done?
I think so. At least, we're a lot closer to spec than we were.
regards, tom
Dear Tom,
I was thinking that any integer attribute of any tuple in a shared
relation would be ok to store a sequence value.
Certainly not --- when there are multiple versions of the tuple because
of MVCC rules, which do you use?
I understand you concern, but I think the troubles depends on how the
Jie Liang wrote:
Does 7.3* support this? Can you tell me a bit more about it, please?
Hash aggregate..?
>I had a similar problem after upgrade to 7.4.2,
>Try:
>SET enable_hashagg = false;
>Before you execute that SELECT stmt
>If you don't want disable it in postgresql.conf
>
>Jie Liang
>
>
Fabien COELHO <[EMAIL PROTECTED]> writes:
> I was thinking that any integer attribute of any tuple in a shared
> relation would be ok to store a sequence value.
Certainly not --- when there are multiple versions of the tuple because
of MVCC rules, which do you use?
regard
Dear Tom,
The "clean" way to handle this would be to extend the bootstrap command
parser to accept a command along the lines of CREATE [SHARED] SEQUENCE
and then add a file in src/include/catalog that defines the shared
user-id-generator sequence. (Look at how pg_shadow is created for
precedent.)
On Fri, Feb 27, 2004 at 07:24:18PM +0100, Margit Schubert-While wrote:
> exec sql begin declare section;
> static int intcur[50][10] = { 0 };
>
> produces :
> ERROR: No multi-dimensional array support for simple data types
So far so good, but which bug are you reporting?
Michael
--
18 matches
Mail list logo
