On 10/21/2011 01:43 PM, Eric McKeeth wrote:
As far as how to use icacls to set
permisions on a directory (as opposed to the files in a directory)
without recursing to all subdirectories, I never did succeed in finding
that out.
Could it depend on the presence or absence of a trailing slash? So
On Wed, Oct 5, 2011 at 1:24 AM, Dave Page wrote:
>
>
> On Wednesday, October 5, 2011, Thomas Kellerer wrote:
> > Dave Page, 04.10.2011 21:46:
>
> >>
> >> We updated our build system to use BitRock 7 today (for unrelated
> >> reasons) which has new features for ACL management. We're going to
> >>
2011/10/20 Tom Lane :
> Pavel Stehule writes:
>> I didn't design a PERFORM statement. There is two views - somebody
>> from sybase's family know so SELECT without into is forwarded to
>> client. This functionality is missing on Oracle's family. Is true so
>> PERFORM statement is strange, but mayb
On Thu, Oct 20, 2011 at 3:01 PM, Tom Lane wrote:
> Pavel Stehule writes:
>> I didn't design a PERFORM statement. There is two views - somebody
>> from sybase's family know so SELECT without into is forwarded to
>> client. This functionality is missing on Oracle's family. Is true so
>> PERFORM sta
Pavel Stehule writes:
> I didn't design a PERFORM statement. There is two views - somebody
> from sybase's family know so SELECT without into is forwarded to
> client. This functionality is missing on Oracle's family. Is true so
> PERFORM statement is strange, but maybe it's open door for sybase'
On Oct 20, 2011, at 11:20 PM, Tom Lane wrote:
> bob.mes...@l-3com.com writes:
>> 2) If I replace the libedit.so with the version in this rpm:
>> libedit-2.11-2.20080712cvs.el5.x86_64.rpm, the command works.
>
>> 3) if I edit the psql script to use the libreadline.so that is
>> install
bob.mes...@l-3com.com writes:
> I am talking about the one that is installed in the PostgreSQL/lib folder,
> not the one from the operating system.
Well, you need to be complaining to whoever provided that build of
Postgres, which is not the upstream project ... and it is definitely
not me person
bob.mes...@l-3com.com writes:
> 2) If I replace the libedit.so with the version in this rpm:
> libedit-2.11-2.20080712cvs.el5.x86_64.rpm, the command works.
> 3) if I edit the psql script to use the libreadline.so that is
> installed on the system (it's looking in the wrong place), t
"Robert Messer" writes:
> postgres=# \l
> *** glibc detected *** /opt/PostgreSQL/9.1/bin/psql.bin: realloc(): invalid
> next size: 0x19510a20 ***
Well, this is interesting, but you're going to need to provide enough
information to let someone else duplicate it. "large database" means
lit
2011/10/20 Tom Lane :
> Valentine Gogichashvili writes:
>> And, ernestly, if it were useless to have SELECT without INTO in plpgsql,
>> there also would be no PERFORM command in plpgsql...
>
> Precisely. Pavel's claim is nonsense. The only real question is how
> useful is it to call it PERFORM i
Valentine Gogichashvili writes:
> And, ernestly, if it were useless to have SELECT without INTO in plpgsql,
> there also would be no PERFORM command in plpgsql...
Precisely. Pavel's claim is nonsense. The only real question is how
useful is it to call it PERFORM instead of SELECT.
"Maruthi Kiran" writes:
> make[1]: Entering directory `/usr/postgis-1.5.3/postgis'
> Makefile.pgxs:17: warning: overriding recipe for target `install'
> /usr/local/pgsql/lib/pgxs/src/makefiles/pgxs.mk:92: warning: ignoring old
> recipe for target `install'
> Makefile.pgxs:63: warning: overriding r
2011/10/20 Merlin Moncure :
> On Thu, Oct 20, 2011 at 2:28 AM, Pavel Stehule
> wrote:
>>>
>>> it would be really a good idea to allow SELECT without INTO in plpgsql.
>>
>> SELECT without INTO is useless in plpgsql - because you have to drop result.
>
> not if you're calling a function:
> select f
The following bug has been logged online:
Bug reference: 6263
Logged by: Robert Messer
Email address: bob.mes...@l-3com.com
PostgreSQL version: 9.1.1 64-bit
Operating system: Red Hat Enterprise Linux Server release 5.4 (Tikanga)
Description:\l causes core dump with la
>
>
> >>
> >> it would be really a good idea to allow SELECT without INTO in plpgsql.
> >
> > SELECT without INTO is useless in plpgsql - because you have to drop
> result.
>
> not if you're calling a function:
> select func();
>
> or calling bunch of functions:
SELECT func(param) FROM some_su
The following bug has been logged online:
Bug reference: 6262
Logged by: Maruthi Kiran
Email address: mnandi...@avineonindia.com
PostgreSQL version: 8.4
Operating system: Linux
Description:while installing postgis in make install
leavingdirectory
Details:
[root@aipl
On Thu, Oct 20, 2011 at 2:28 AM, Pavel Stehule wrote:
>>
>> it would be really a good idea to allow SELECT without INTO in plpgsql.
>
> SELECT without INTO is useless in plpgsql - because you have to drop result.
not if you're calling a function:
select func();
merlin
--
Sent via pgsql-bugs ma
2011/10/20 Valentine Gogichashvili :
>>
>> I suppose you could argue that selecting a value and implicitly throwing
>> it away is confusing to novices, but on the other hand I've seen a whole
>> lot of novices confused by the need to write PERFORM instead of SELECT.
>> I think it wouldn't be an unr
18 matches
Mail list logo
