-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
DOH! *facepalm* Thanks Tom!
I read docs on set_config() and didn't think to check CREATE FUNCTION.
It does make sense, and now that you point it out, I do remember that
too. I didn't think to check it because this function is *not* secdef,
which is w
postgre...@thewickedtribe.net writes:
> So, found this in 8.3 but tested and it effects everything up to 9.1.1. If
> search_path on a function is set to anything, calls to set_config() with
> is_local = true inside that function have no effect.
Isn't that exactly what the CREATE FUNCTION referenc
The following bug has been logged on the website:
Bug reference: 6316
Logged by: Jon Erdman
Email address: postgre...@thewickedtribe.net
PostgreSQL version: 9.1.1
Operating system: Ubuntu
Description:
Hi Tom! :)
So, found this in 8.3 but tested and it effects everyt
On 1 December 2011 22:50, Alvaro Herrera wrote:
>
> Excerpts from Tom Lane's message of jue dic 01 18:32:58 -0300 2011:
>> Boszormenyi Zoltan writes:
>> > 2011-12-01 20:09 keltezéssel, rep.dot@gmail.com írta:
>> >> Binding for "OFFSET :offset" works fine but binding for a
>> >> "FETCH NEXT :
Alvaro Herrera writes:
> Excerpts from Tom Lane's message of jue dic 01 18:32:58 -0300 2011:
>> Well, actually it is supported, but you missed the fine print where it
>> says that you have to add parentheses if the offset or count isn't a
>> simple integer constant. I'll apply a patch to make tha
Excerpts from Tom Lane's message of jue dic 01 18:32:58 -0300 2011:
> Boszormenyi Zoltan writes:
> > 2011-12-01 20:09 keltezéssel, rep.dot@gmail.com írta:
> >> Binding for "OFFSET :offset" works fine but binding for a
> >> "FETCH NEXT :next
> >> ROWS ONLY" raises:
> >> syntax error at or nea
Boszormenyi Zoltan writes:
> 2011-12-01 20:09 keltezéssel, rep.dot@gmail.com Ãrta:
>> Binding for "OFFSET :offset" works fine but binding for a
>> "FETCH NEXT :next
>> ROWS ONLY" raises:
>> syntax error at or near "$2"
>> SELECT * FROM foo OFFSET $1 ROWS FETCH NEXT $2 ROWS ONLY
> This is n
2011-12-01 20:09 keltezéssel, rep.dot@gmail.com írta:
> The following bug has been logged on the website:
>
> Bug reference: 6315
> Logged by: Bernhard Reutner-Fischer
> Email address: rep.dot@gmail.com
> PostgreSQL version: 9.1.1
> Operating system: linux
> Description
On Wed, Nov 30, 2011 at 11:19 PM, Suneel Kumar M
wrote:
> I have downloaded postgresql-8.4.9.tar.gz and compiled for X86 and installed
> the package it is working fine.
Great. But why use a version that is two major releases out of date?
> Now I wanted to Cross compile and port it to my Target.
The following bug has been logged on the website:
Bug reference: 6315
Logged by: Bernhard Reutner-Fischer
Email address: rep.dot@gmail.com
PostgreSQL version: 9.1.1
Operating system: linux
Description:
Binding for "OFFSET :offset" works fine but binding for a "FET
d.reri...@healthcareoss.com writes:
> Simply set a varchar field in your db to the following string:
> !"#$%'()*+,-/:;=?@[\]^_`{|}~&<>
> I know, I know, who would do this, right? Well, its for a certification.
> The like command works fine up with escapes up to:
> !"#$%''()*+,-/:;=?@[%
Doesn
wrote:
> Simply set a varchar field in your db to the following string:
> !"#$%'()*+,-/:;=?@[\]^_`{|}~&<>
Do you have standard_conforming_strings = on?
> The like command works fine up with escapes up to:
> !"#$%''()*+,-/:;=?@[%
> Notice, I added the % to the end. However, if you go any
Josh Kupershmidt writes:
> Here's a backtrace from 9.1 tip with CFLAGS="-O0", server logs are as before:
> Program received signal SIGBUS, Bus error.
> 0x00c9716b in ?? () from /lib/i386-linux-gnu/libc.so.6
> (gdb) bt
> #0 0x00c9716b in ?? () from /lib/i386-linux-gnu/libc.so.6
> #1 0x082b3b2f i
The following bug has been logged on the website:
Bug reference: 6314
Logged by: David Rericha
Email address: d.reri...@healthcareoss.com
PostgreSQL version: 8.4.5
Operating system: OpenSuSE 11.4 64-bit
Description:
Simply set a varchar field in your db to the followi
dmigow...@ikoffice.de writes:
> PostgreSQL version: 8.3.16
> In my application I receive deadlocks from time to time, reported by an
> error message like this:
> ERROR: deadlock detected
> SQL Status:40P01
> Detail:Process 30812 waits for ShareLock on transaction 278158200; blocked
> by process 2
Hi,
I have downloaded postgresql-8.4.9.tar.gz and compiled for X86 and installed
the package it is working fine.
Now I wanted to Cross compile and port it to my Target.
Target Details:
OS: Linux - Slackware 12
CPU: Freescale ColdFire MCF54418CMJ250.
CPU Architecture: m68k
Please let me know w
The following bug has been logged on the website:
Bug reference: 6313
Logged by: Daniel Migowski
Email address: dmigow...@ikoffice.de
PostgreSQL version: 8.3.16
Operating system: Linux
Description:
In my application I receive deadlocks from time to time, reported by a
The following bug has been logged on the website:
Bug reference: 6312
Logged by: Magnus hagander
Email address: mag...@hagander.net
PostgreSQL version: Unsupported/Unknown
Operating system: Linux
Description:
This is a test bug report. It seems bug reporting got broke
Applied.
---
Bruce Momjian wrote:
> Pilling, Michael wrote:
> > Hi Kevin,
> >
> > Thanks for that. Point entirely taken. I think what I would add would
> > be in the table 9-1 of operators, an extra column filled in only fo
On Wed, Nov 30, 2011 at 10:50 PM, Tom Lane wrote:
> Josh Kupershmidt writes:
>> On Wed, Nov 30, 2011 at 9:17 PM, Tom Lane wrote:
> It might be worth recompiling at -O0, first to see if that changes the
> behavior and second to see if it changes the reported stack trace.
Here's a backtrace from
20 matches
Mail list logo
