ot;trusted" and "untrusted" procedural
languages. plpgsql and plperl are "trusted" while plperlu and plpythonu
are "untrusted". See this link for an explanation:
https://www.postgresql.org/docs/current/static/plperl-trusted.html
Hope this helps.
Joe
--
Crunch
Thank you. Your response helped me figure out why pgp_pub_decrypt wasn't
working for data that was encrypted outside of pgcrypto. The marker you
mention must be added by pgp_pub_encrypt? Perhaps it's worth mentioning in
the documentation that pgp_pub_decrypt is only intended be used on data
encrypt
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.5/static/pgcrypto.html
Description:
I believe the first argument should be of type 'text'. Especially
considering the paragraph that follows discusses how passing in bytea is
disallowed.
-
but
it is mentioned here:
http://www.postgresql.org/docs/9.4/interactive/sql-select.html#SQL-FROM
8<---
alias
A substitute name for the FROM item [...] If an alias is written, a
column alias list can also be written to provide substitute names for
one or more columns of the table.
8<
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/24/2014 08:25 PM, Joe Conway wrote:
> Shouldn't the reference to work_mem here:
>
> "Allow in-memory sorts to use their full memory allocation (Jeff
> Janes)"
> http://www.postgresql.org/docs/9.3/interact
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shouldn't the reference to work_mem here:
"Allow in-memory sorts to use their full memory allocation (Jeff Janes)"
http://www.postgresql.org/docs/9.3/interactive/release-9-3.html#AEN114956
actually be referencing maintenance
mind the rubbish screenshot app
> I'm using heavily compresses the image, so elements aren't appearing
> as clear as they should do.
>
> http://www.flickr.com/photos/dark_ixion/4937010683/sizes/o/
+1
I really like this version.
Joe
--
Joe Conway
credativ LLC: http://ww
contrib modules I've worked on (or I can do it if you'd prefer).
In any case +1 for a uniform policy, and +1 for removing credits from
documentation.
Joe
---(end of broadcast)---
TIP 6: explain analyze is your friend
e I'm just starting to do
business travel again), but I'll take responsibility to write something
up if you'd like.
Joe
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Jim C. Nasby wrote:
On Tue, Jan 03, 2006 at 04:20:38PM -0800, Joe Conway wrote:
Well I like {prefix}/doc given that's how dblink is already set up ;-)
By {prefix} do you mean where PostgreSQL is being installed? If so, that
would be highly non-standard. I think what you'd want
Tom Lane wrote:
Joe Conway <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
It's not only the downstream packagers that have missed these: the
Makefiles don't install them either.
It'd be a good idea to settle on what we want the installed file layout
to be --- do we need to
output PDF file not finished!
Transcript written on postgres.log.
make: *** [postgres.pdf] Error 1
make: *** Deleting file `postgres.pdf'
Any ideas?
Thanks,
Joe
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
ht
Bruce Momjian wrote:
What had me really confused was the first release item:
Allow polymorphic SQL functions (Joe)
How does an SQL function query the data types passed to it? Once I
saw that I thought I didn't underestand what polymorphic functions
were.
It doesn't need to. For exampl
Bruce Momjian wrote:
http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-7-4
I need people to check this and help me with the items marked 'bjm'. I
am confused about the proper text for those sections.
> Allow polymorphic SQL functions (Joe)
> bjm ??
What i
14 matches
Mail list logo