Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
If you don't re-run a contrib module's sql script then you don't get any
new functions that may have been added to the module. So I think the
real issue here is that we ought to deprecate the idea of skipping that
Bruce Momjian wrote:
Tom Lane wrote:
Marko Kreen [EMAIL PROTECTED] writes:
On 11/10/07, Bruce Momjian [EMAIL PROTECTED] wrote:
OK, first question. How would someone have the 8.0 signatures in 8.2?
Don't they reinstall pgcrypto for every major release?
Why reinstall if the
Bruce Momjian [EMAIL PROTECTED] writes:
I have cleaned up the contrib install/uninstall to be more consistent,
used CREATE OR REPLACE function consisently, and removed transaction
blocks.
... and broken the buildfarm ...
regards, tom lane
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
I have cleaned up the contrib install/uninstall to be more consistent,
used CREATE OR REPLACE function consisently, and removed transaction
blocks.
... and broken the buildfarm ...
OK, fixed, thanks.
--
Bruce Momjian [EMAIL
On 11/7/07, Bruce Momjian [EMAIL PROTECTED] wrote:
OK, should we add a mention in the 8.2.6 release notes or put it in the
8. notes and figure if someone is upgrading they will read the 8.2
notes? What would the description be?
Note about pgcrypto - the functions were made STRICT in 8.1
and
Marko Kreen wrote:
On 11/7/07, Bruce Momjian [EMAIL PROTECTED] wrote:
OK, should we add a mention in the 8.2.6 release notes or put it in the
8. notes and figure if someone is upgrading they will read the 8.2
notes? What would the description be?
Note about pgcrypto - the functions
On 11/10/07, Bruce Momjian [EMAIL PROTECTED] wrote:
OK, first question. How would someone have the 8.0 signatures in 8.2?
Don't they reinstall pgcrypto for every major release?
Why reinstall if the functions come from dump?
At least in skype we stumbled on the problem. But if the reinstall
Marko Kreen [EMAIL PROTECTED] writes:
On 11/10/07, Bruce Momjian [EMAIL PROTECTED] wrote:
OK, first question. How would someone have the 8.0 signatures in 8.2?
Don't they reinstall pgcrypto for every major release?
Why reinstall if the functions come from dump?
At least in skype we
Marko Kreen wrote:
On 11/10/07, Bruce Momjian [EMAIL PROTECTED] wrote:
OK, first question. How would someone have the 8.0 signatures in 8.2?
Don't they reinstall pgcrypto for every major release?
Why reinstall if the functions come from dump?
At least in skype we stumbled on the
Tom Lane wrote:
Marko Kreen [EMAIL PROTECTED] writes:
On 11/10/07, Bruce Momjian [EMAIL PROTECTED] wrote:
OK, first question. How would someone have the 8.0 signatures in 8.2?
Don't they reinstall pgcrypto for every major release?
Why reinstall if the functions come from dump?
At
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
If you don't re-run a contrib module's sql script then you don't get any
new functions that may have been added to the module. So I think the
real issue here is that we ought to deprecate the idea of skipping that
step, period.
The
Marko Kreen wrote:
On 11/6/07, Bruce Momjian [EMAIL PROTECTED] wrote:
Alvaro Herrera wrote:
Tom, how about putting a note about that into next 8.2 minor
release notes? (8.3 too?) Something like You need to refresh
pgcrypto functions, because since rel 8.2 the code depends
On 11/6/07, Bruce Momjian [EMAIL PROTECTED] wrote:
Alvaro Herrera wrote:
Tom, how about putting a note about that into next 8.2 minor
release notes? (8.3 too?) Something like You need to refresh
pgcrypto functions, because since rel 8.2 the code depends
on functions being tagged
Bruce Momjian wrote:
Marko Kreen wrote:
On 8/24/07, Manuel Sugawara [EMAIL PROTECTED] wrote:
If something is not going a work (or is going a work in a different
way) in some version after loading a shot form a previous one I think
it should be documented or some kind of backwards
Alvaro Herrera wrote:
If something is not going a work (or is going a work in a different
way) in some version after loading a shot form a previous one I think
it should be documented or some kind of backwards compatibility
mechanism should be provided.
That's a valid
Marko Kreen wrote:
On 8/24/07, Manuel Sugawara [EMAIL PROTECTED] wrote:
Tom Lane [EMAIL PROTECTED] writes:
Manuel Sugawara [EMAIL PROTECTED] writes:
Marko Kreen [EMAIL PROTECTED] writes:
In 8.0 the pgcrypto functions were non-strict and checked for NULLs.
In 8.1 they were made
On 8/24/07, Manuel Sugawara [EMAIL PROTECTED] wrote:
Tom Lane [EMAIL PROTECTED] writes:
Manuel Sugawara [EMAIL PROTECTED] writes:
Marko Kreen [EMAIL PROTECTED] writes:
In 8.0 the pgcrypto functions were non-strict and checked for NULLs.
In 8.1 they were made STRICT.
In 8.2 the NULL
On 8/24/07, Manuel Sugawara [EMAIL PROTECTED] wrote:
Manuel Sugawara [EMAIL PROTECTED] writes:
I have a simple query that uses digest(data, 'sha1') and consistently
crashes the backend
The problem is with null arguments:
ciencias=# select digest(null, 'sha1');
In 8.0 the pgcrypto
Manuel Sugawara wrote:
I have a simple query that uses digest(data, 'sha1') and consistently
crashes the backend
The problem is with null arguments:
ciencias=# select digest(null, 'sha1');
el servidor ha cerrado la conexión inesperadamente,
Can you check if the function is defined STRICT?
Marko Kreen [EMAIL PROTECTED] writes:
On 8/24/07, Manuel Sugawara [EMAIL PROTECTED] wrote:
Manuel Sugawara [EMAIL PROTECTED] writes:
I have a simple query that uses digest(data, 'sha1') and consistently
crashes the backend
The problem is with null arguments:
ciencias=# select
Manuel Sugawara [EMAIL PROTECTED] writes:
Marko Kreen [EMAIL PROTECTED] writes:
In 8.0 the pgcrypto functions were non-strict and checked for NULLs.
In 8.1 they were made STRICT.
In 8.2 the NULL check were removed from code.
Not an smart move IMHO, I didn't create the function, it was
Tom Lane [EMAIL PROTECTED] writes:
Manuel Sugawara [EMAIL PROTECTED] writes:
Marko Kreen [EMAIL PROTECTED] writes:
In 8.0 the pgcrypto functions were non-strict and checked for NULLs.
In 8.1 they were made STRICT.
In 8.2 the NULL check were removed from code.
Not an smart move IMHO, I
Manuel Sugawara [EMAIL PROTECTED] writes:
Hi,
I have a simple query that uses digest(data, 'sha1') and consistently
crashes the backend
The problem is with null arguments:
ciencias=# select digest(null, 'sha1');
el servidor ha cerrado la conexión inesperadamente,
probablemente
23 matches
Mail list logo
