"Marko Kreen" <[EMAIL PROTECTED]> writes:
> The fix should be in combo_decrypt() because other code
> should not need to guess whether zero-length input is
> allowed or not.
> Patch attached.
Thanks -- applied in all branches back to 7.3.
regards, tom lane
--
Tom Lane wrote:
> Dave Page <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
>>> The actual prohibition is on inserting a new pg_class row, which Dave's
>>> command is trying to do because he's trying to create a composite type.
>
>> If thats the case, then there's another inconsistency as I can ins
Dave Page <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> The actual prohibition is on inserting a new pg_class row, which Dave's
>> command is trying to do because he's trying to create a composite type.
> If thats the case, then there's another inconsistency as I can insert a
> pg_class row man
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
>> Dave Page wrote:
>>> - "are currently disallowed" implies that sometimes it is allowed. How
>>> does one control that, or is it implying something that is not the case,
>>> or only the case in unusual circumstances such as a standalone
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Dave Page wrote:
>> - "are currently disallowed" implies that sometimes it is allowed. How
>> does one control that, or is it implying something that is not the case,
>> or only the case in unusual circumstances such as a standalone backend?
> It is all
Dave Page wrote:
> - "are currently disallowed" implies that sometimes it is allowed. How
> does one control that, or is it implying something that is not the case,
> or only the case in unusual circumstances such as a standalone backend?
It is allowed in standalone mode AFAIR (maybe when specify
Tom Lane wrote:
> Dave Page <[EMAIL PROTECTED]> writes:
>> Should this work, or at least give a more appropriate error message?
>> demo=# CREATE TYPE pg_catalog.mytype AS (data text);
>> ERROR: permission denied to create "pg_catalog.mytype"
>> DETAIL: System catalog modifications are currently d
Dave Page <[EMAIL PROTECTED]> writes:
> Should this work, or at least give a more appropriate error message?
> demo=# CREATE TYPE pg_catalog.mytype AS (data text);
> ERROR: permission denied to create "pg_catalog.mytype"
> DETAIL: System catalog modifications are currently disallowed.
Seems like
Ruediger Kemmler wrote:
> Dear Dave,
>
> I have illustrated the problem in the attached file. It seems that the box
> for the destination folder is hidden after the first click in the upper box.
I cannot reproduce this problem at all - can anyone else?
Regards, Dave.
>
>> -Ursprüngliche
Should this work, or at least give a more appropriate error message?
demo=# SELECT version();
version
--
PostgreSQL 8.2.4 on i686-pc-mingw32, compiled by GCC gcc.exe (
On 8/23/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Ken Colson" <[EMAIL PROTECTED]> writes:
> > this statement:
> > select decrypt(''::bytea,'password','bf')
> > causes the postgresql backend to crash:
> > This seems to be a 64bit problem.
>
> Reproduced here in HEAD. The problem is here:
> 293
Tom Lane wrote:
"sapna kapoor" <[EMAIL PROTECTED]> writes:
some tables are giving error :
ERROR: invalid page header in block 32655 of relation "" while
accessing.
Some are giving
ERROR: could not access status of transaction 1778384896
DETAIL: could not open file "pg_clog/06A0": No s
Alvaro Herrera wrote:
Russell Smith wrote:
The issue is output, not input.
SET datestyle='dmy';
SELECT '03-03-2004'::date
Will return '2007-03-03', not 03-03-2004 as is the set datestyle.
You are aware that DateStyle controls both input and output,
_separately_, yes?
No, I've RTFM'd to
13 matches
Mail list logo
