Having read through this thread, the consensus seems to be that we don't
want this patch as it is (and I agree with that).
As I understand it, you are trying to solve two problems:
1. Passing parameters to a DO statement. You could quote the parameters
and inline them in the block itself in th
> On Monday, September 24, 2012 12:24 AM Alvaro Herrera wrote:
> Excerpts from Amit kapila's message of sáb sep 22 01:14:40 -0300 2012:
> > On Friday, September 21, 2012 6:50 PM Alvaro Herrera wrote:
> > Excerpts from Amit Kapila's message of vie sep 21 02:26:49 -0300
> 2012:
> > > On Thursday, Sep
"Karl O. Pinc" writes:
> The attached patch documents the oid column of those
> system catalogs having an oid.
I think this is fundamentally wrong, or at least misleading, because it
documents OID as if it were an ordinary column. Somebody who did
"select * from pg_class" and didn't see any "oid
Hi,
Patch to add CREATE TABLE AS to the See Also: section
of the CREATE TABLE docs.
Against git master.
(Builds, as do all the previous doc patches.)
Karl
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
diff --git a/doc/src/sgml/ref/create_table.
Hi,
Adds a caution to the pg_restore docs
Against git master.
Karl
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml
index 488d8dc..ad42d38 100644
--- a/doc/src/sgm
Hi,
The attached patch documents the oid column of those
system catalogs having an oid.
Distinguish system catalogs with an oid from those without
and make the primary key clear to the newbie.
Found catalogs with an oid by querying a 9.2 installation:
select pg_class.relkind, pg_class.relname
Attached is version 2. The sgml did not build.
On 09/23/2012 12:24:27 AM, Karl O. Pinc wrote:
> Whoops. Do over. Sent the wrong file.
>
> On 09/23/2012 12:19:07 AM, Karl O. Pinc wrote:
> > On 09/21/2012 10:54:05 AM, Karl O. Pinc wrote:
> > > On 09/20/2012 12:24:49 PM, Karl O. Pinc wrote:
> > >
On Mon, Sep 24, 2012 at 1:14 AM, Satoshi Nagayasu wrote:
> 2012/09/23 12:37, Greg Sabino Mullane wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: RIPEMD160
> >
> >
> >>> I think it's time to consider some *umbrella project* for maintaining
> >>> several small projects outside the core.
> >
On Sun, 2012-09-23 at 22:20 +0800, Rural Hunter wrote:
> Ah yes, seems I used a wrong parameter. The --locale='zh_CN.utf8'
> works. --locale='zh_CN.UTF8' also works. But still the question is,
> should the encoding name be case sensitive?
PostgreSQL treats encoding names as case insensitive.
Bu
The patch I reviewd is listed among CommitFest 2012-09 patches. I hope
it can be of some help, despite the fact, that I don't really feel like
being terribly qualified here.
Submission review
The patch goes cleanly against v9.3, as fetched by clonig current HEAD
from postgres git repository:
On 09/22/2012 01:57 PM, Stephen Frost wrote:
Andrew,
Below is the patch that I mentioned at pgOpen. I'm pretty sure my
silly github pull request got screwed up anyway, so probably best to
ignore it. Regardless, please let me know what you think. I'd be
happy to rework it to opera
Excerpts from Jan Urbański's message of dom sep 23 14:21:53 -0300 2012:
> There's a typo in src/tools/RELEASE_CHANGES
>
> It just ticked off my OCD I guess...
Pushed, thanks.
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Excerpts from Amit kapila's message of sáb sep 22 01:14:40 -0300 2012:
> On Friday, September 21, 2012 6:50 PM Alvaro Herrera wrote:
> Excerpts from Amit Kapila's message of vie sep 21 02:26:49 -0300 2012:
> > On Thursday, September 20, 2012 7:13 PM Alvaro Herrera wrote:
>
> > > > Well, there is a
There's a typo in src/tools/RELEASE_CHANGES
It just ticked off my OCD I guess...
Cheers,
Jan
diff --git a/src/tools/RELEASE_CHANGES b/src/tools/RELEASE_CHANGES
new file mode 100644
index 5f1277a..aba1630
*** a/src/tools/RELEASE_CHANGES
--- b/src/tools/RELEASE_CHANGES
*** Then doing i
2012/09/23 12:37, Greg Sabino Mullane wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
>
>>> I think it's time to consider some *umbrella project* for maintaining
>>> several small projects outside the core.
>>
>> Well, that was pgfoundry, and it didn't work out.
>
> I'm not sure
We historically have connection pooling as an external thing; with the high
degree to which people keep implementing and reimplementing this, I think
*something* more than we have ought to be built in.
This, with perhaps better implementation, might be an apropos start.
Parallel with LDAP: it tak
于2012年9月23日 20:33:48,Peter Eisentraut写到:
On Fri, 2012-09-21 at 17:16 +0800, Rural Hunter wrote:
If I run initdb with '-E zh_CN.utf8', it will tell me there
is no such charset in the system.
Because that is the name of a locale, not an encoding.
I found a workaround to run initdb
with '--lc
On 23-09-2012 07:50, Satoshi Nagayasu wrote:
> I have just written the first PoC code to enable load balancing
> in the libpq library.
>
Your POC is totally broken. Just to point out two problems: (i) semicolon (;)
is a valid character for any option in the connection string and (ii) you
didn't th
On Fri, 2012-09-21 at 17:16 +0800, Rural Hunter wrote:
> If I run initdb with '-E zh_CN.utf8', it will tell me there
> is no such charset in the system.
Because that is the name of a locale, not an encoding.
> I found a workaround to run initdb
> with '--lc-collate=zh_CN.utf8 --lc-ctype=zh_CN.
Hi all,
I have just written the first PoC code to enable load balancing
in the libpq library.
This libpq enhancement is intended to allow PostgreSQL users to
take advantage of the replication in easier way.
With using this patch, PQconnectdb() function accepts multiple
connection info strings, a
20 matches
Mail list logo
