The following bug has been logged online:
Bug reference: 1310
Logged by: Tom O'Connell
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 Beta
Operating system: Windows 2000 Professional
Description:libecpg.dll missing from msi package
Details:
The libecp
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> DECLARE
> v_MyRow ut_TestSearch%rowtype;
> a_OrderBy ALIAS FOR $1;
> a_SortAsc ALIAS FOR $2;
> BEGIN
> FOR v_MyRow IN
> SELECT Colum1,
> Column2,
> Co
The following bug has been logged online:
Bug reference: 1309
Logged by: Christina Zhang
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.1
Operating system: Linux
Description:PL/PGSQL function: ORDER BY does not accept variables
Details:
When we write
On Tue, 9 Nov 2004, PostgreSQL Bugs List wrote:
>
> Bug reference: 1308
> Logged by: Simon Lesage-Tremblay
> Email address: [EMAIL PROTECTED]
>
> Description:Bug with JDBC driver on duplicate
>
> Details:
>
> My problem is when I insert a record that have a proble
The following bug has been logged online:
Bug reference: 1308
Logged by: Simon Lesage-Tremblay
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.2
Operating system: Linux
Description:Bug with JDBC driver on duplicate
Details:
I have the version 7.4.2 of
Without USERLIMIT, we could easily change the rules to make ALTER USER
work the way you want: we'd say you have to be superuser to issue ALTER
USER or ALTER DATABASE with a SUSET variable (already true), and then
the value can be adopted at session start in all cases since we can
then
treat pg_sha
Sean Chittenden <[EMAIL PROTECTED]> writes:
>> It strikes me that a more useful definition would be to say that you
>> must be superuser, period, to install an ALTER USER/DATABASE value for
>> any USERLIMIT variable; and then we could treat these values as
>> privileged for USERLIMIT purposes. Thi
doh! So much for that idea. There's no real way to have some
useconfig variables run by the super user and some run by the session
user. My workaround is to have the program call a SECURITY DEFINER
function, but I'd be nice to be able to remove that hack.
Yeah, the whole concept of USERLIMIT GUC
On Mon, Nov 08, 2004 at 08:06:02PM -0500, Tom Lane wrote:
> I believe that if VACUUM wants to delete a tuple that is on the same
> physical page that a cursor is currently stopped on, the vacuum has to
> wait until the cursor moves off that page. So the vacuum could
> definitely be blocked by the
Sean Chittenden <[EMAIL PROTECTED]> writes:
> doh! So much for that idea. There's no real way to have some
> useconfig variables run by the super user and some run by the session
> user. My workaround is to have the program call a SECURITY DEFINER
> function, but I'd be nice to be able to rem
I've got a particular database account that connects/disconnects
hundreds of times a second, literally (email delivery agent). Being
the ever ready logger that I am, I have a number of logging bits turned
on to help me identify problems when they come up. In this case, I'm
not worried about a
11 matches
Mail list logo
