On 06/22/2017 04:29 AM, Gerard Matthews wrote:
> It's under this page on the
> docs https://www.postgresql.org/docs/9.1/static/ecpg-dynamic.html.
Perhaps a bit confusing but notice the title in the top middle of the
page: "Chapter 33. ECPG - Embedded SQL in C"
That is definitely not what you are
On 09/21/2015 06:04 PM, Amir Rohan wrote:
> This belongs in the page describing SELECT, and though I've looked I haven't
> found it. If I'm wrong (
> I did look again just now), please correct me.
Feel free to submit a doc patch if you feel it needs to be improved, but
it is mentioned here:
htt
-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
_work_mem?
Joe
- --
Joe Conway
credativ LLC: http://www.credativ.us
Linux, PostgreSQL, and general Open Source
Training, Service, Consulting, & 24x7 Support
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http
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
Tom Lane wrote:
As of CVS HEAD, some of the contrib module documentation pages have
extensive credit screeds, eg
http://developer.postgresql.org/pgdocs/postgres/cube.html
and some just have the author's name, with or without an link,
and some don't have anything at all.
This bothers me; it seem
Peter Eisentraut wrote:
Tom Lane wrote:
Should we give VALUES its own reference page? That doesn't quite
seem helpful either. cc'ing to pgsql-docs for ideas.
This is probably the sort of thing that should be explained part II "The
SQL Language". In particular, section 7.2 is about table e
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
Peter Eisentraut wrote:
I've upgraded our documentation to DocBook V4.2 SGML. I was able to
install 4.2 by going to http://www.docbook.org/sgml/4.2/, unzipping the
file in a suitable place and adding the docbook.cat file to the
environment variable SGML_CATALOG_FILES. Packages are also available
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 example:
CREATE
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 isn't clear about this
12 matches
Mail list logo
