On Sat, February 23, 2013 00:09, Mike Toews wrote:
>
> Type info can be viewed with "\d mytable", however often I'd like to see
> the type (and typmod) info in SELECT queries with psql, similar to pgAdmin
> III. For example:
>
> my_db=# \pset type
> my_db=# SELECT * FROM my_table;
> gid | desc
Hi,
What do you think about adding hooks for transaction ID and snapshot
acquisition? Those hooks could be located in AssignTransactionId:xact.c for
transaction ID and GetTransactionSnapshot:snapmgr.c for snapshots.
This is useful for multi-master applications that use external tools to
feed with
2013/2/23 Stephen Frost :
> Pavel,
>
> * Pavel Stehule (pavel.steh...@gmail.com) wrote:
>> We cannot to remove minimal_error_message() because there
>> are >>two<< SQL queries and if we do fault tolerant oid lookup, then
>> still pg_get_functiondef can raise exception.
>
> Why is that? lookup_fun
Pavel,
* Pavel Stehule (pavel.steh...@gmail.com) wrote:
> We cannot to remove minimal_error_message() because there
> are >>two<< SQL queries and if we do fault tolerant oid lookup, then
> still pg_get_functiondef can raise exception.
Why is that? lookup_function_oid() only collects the oid to
On Fri, 2013-02-22 at 03:42 -0500, Tom Lane wrote:
> I still think it's incumbent on OSSP to fix this, not us. Or if
> they've gone dead, maybe we need to start looking for some other
> source of uuid support.
ossp-uuid still works, in spite of its age, but I have started a
replacement here if p
Zoltán,
* Zoltán Böszörményi (z...@cybertec.at) wrote:
> The patch now passed "make check" in both cases.
Is v29 the latest version of this patch..?
Looking through the patch, I've noticed a couple of things:
First off, it's not in context diff format, which is the PG standard for
patch submiss
> That feels completely wrong to me. For one thing, I can't think of
> any ALTER commands to populate or remove data. What did you think
> of the idea of something like DISCARD MATERIALIZED VIEW DATA as a
> new statment? Or maybe RESET MATERIALIZED VIEW?
I prefer RESET, especially since it cou
Hi hackers,
Type info can be viewed with "\d mytable", however often I'd like to see
the type (and typmod) info in SELECT queries with psql, similar to pgAdmin
III. For example:
my_db=# \pset type
my_db=# SELECT * FROM my_table;
gid | description| width
integer | character varyi
On Thu, Feb 21, 2013 at 12:52 PM, Alvaro Herrera
wrote:
>> What if the object that gets whacked around is one of the named
>> objects rather than some dependency thereof? Suppose for example that
>> the event trigger drops the same object that the user tried to drop.
>> We need to error out clean
On Thu, Feb 21, 2013 at 12:47 PM, Alvaro Herrera
wrote:
> You're misunderstanding. If you do DROP EVENT TRIGGER, the DDL_DROP
> event won't fire at all. So no matter how messed up your system is, you
> can always fix it by simply dropping the event trigger.
>
> What I was saying is that if you h
On 2013-02-22 16:58:37 -0300, Alvaro Herrera wrote:
> Andres Freund wrote:
> > On 2013-02-13 12:09:37 -0300, Alvaro Herrera wrote:
> > > Here's an updated version of pg_xlogdump. This is rebased on top of the
> > > committed xlogreader, palloc restructuring and libpgcommon, PG_RMGR
> > > stuff, an
Andres Freund wrote:
> On 2013-02-13 12:09:37 -0300, Alvaro Herrera wrote:
> > Here's an updated version of pg_xlogdump. This is rebased on top of the
> > committed xlogreader, palloc restructuring and libpgcommon, PG_RMGR
> > stuff, and is basically a revamped version of what Andres submitted in
On Feb 22, 2013, at 9:37 AM, Robert Haas wrote:
> What I think is NOT tolerable is choosing a set of short but arbitrary
> names which are different from anything that we have now and
> pretending that we'll want to use those again for the next data type
> that comes along. That's just wishful t
On Thu, Feb 21, 2013 at 1:16 PM, Merlin Moncure wrote:
> Well, for case the of operator, it means whatever we reserve to mean.
> Very much agree on limitations of symbolic representation of behaviors
> (especially since some of the best ones were reserved by SQL or other
> acctors), so I think the
On Thu, Feb 21, 2013 at 11:55 AM, Michael Paquier
wrote:
> A ShareUpdateExclusiveLock is taken on index or table that is going to be
> rebuilt just before calling ReindexRelationConcurrently. So the solution I
> have here is to make REINDEX CONCURRENTLY fail for session 2. REINDEX
> CONCURRENTLY i
On Feb 22, 2013, at 12:42 AM, Tom Lane wrote:
> Yeah, you did:
> http://www.postgresql.org/message-id/62fdd311-1afc-4296-95d8-5751d1407...@justatheory.com
>
> I still think it's incumbent on OSSP to fix this, not us. Or if
> they've gone dead, maybe we need to start looking for some other
> sou
Ibrar Ahmed writes:
> * In case we have hstore--1.3.sql file and want to install that file, but
> failed because of default_full_version.
That's now fixed, please see the Extension Templates patch at
http://www.postgresql.org/message-id/m21uc8l4j8@2ndquadrant.fr
Where you will even find r
Hi,
Please find attached v3 of the Extension Templates patch, with full
pg_dump support thanks to having merged default_full_version, appended
with some regression tests now that it's possible.
The patch also implements ALTER RENAME and OWNER facilities for those
new templates objects.
Dimitri F
On 22 February 2013 14:10, Tom Lane wrote:
> Thom Brown writes:
>> Bit of an issue with selecting rows:
>
> Ooops, looks like I screwed up the logic for whole-row references.
> Will fix, thanks for the test case!
Retried after your changes and all is well. Thanks Tom.
--
Thom
--
Sent via p
Thom Brown writes:
> Bit of an issue with selecting rows:
Ooops, looks like I screwed up the logic for whole-row references.
Will fix, thanks for the test case!
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to y
Michael Paquier writes:
> On Fri, Feb 22, 2013 at 5:13 PM, Tom Lane wrote:
>> Wups ... for some reason it's "use_remote_estimate" in the docs. Thinko
>> on my part probably --- although on reflection, maybe that's a better
>> name anyway?
> Indeed, use_remote_estimate is better. use_remote_expl
On 21 February 2013 10:30, Tom Lane wrote:
> Shigeru Hanada writes:
>> [ postgres_fdw.v5.patch ]
>
> Applied with a lot of revisions.
Bit of an issue with selecting rows:
postgres=# SELECT * FROM animals;
id | animal_name | animal_type | lifespan
+-+-+--
1
On Fri, Feb 22, 2013 at 5:13 PM, Tom Lane wrote:
> Michael Paquier writes:
> > While testing a bit this feature, I noticed that use_remote_explain is
> > available in the list of options for FOREIGN TABLE and SERVER but this is
> > not specified in the docs:
> > http://www.postgresql.org/docs/de
On 15.02.2013 10:33, Kyotaro HORIGUCHI wrote:
Sorry, I omitted to show how we found this issue.
In HA DB cluster cosists of Pacemaker and PostgreSQL, PostgreSQL
is stopped by 'pg_ctl stop -m i' regardless of situation.
That seems like a bad idea. If nothing else, crash recovery can take a
lon
On 14.02.2013 19:18, Fujii Masao wrote:
Yes. And the resource agent for streaming replication in Pacemaker (it's the
OSS clusterware) is the user of that archive recovery scenario, too. When it
starts up the server, it always creates the recovery.conf and starts the server
as the standby. It cann
On Wednesday, February 20, 2013 5:25 PM Etsuro Fujita wrote:
> Hi Amit,
>
> Thank you for the review.
Etsuro-san, you are welcome.
> > From: Amit Kapila [mailto:amit.kap...@huawei.com]
>
> > >> Test case issues:
> > >> --
> > >> 1. "Broken pipe" is not handled in case of psql "
On 22.02.2013 02:13, Michael Paquier wrote:
On Thu, Feb 21, 2013 at 11:09 PM, Heikki Linnakangas<
hlinnakan...@vmware.com> wrote:
On 15.02.2013 15:49, Heikki Linnakangas wrote:
Attached is a patch for git master. The basic idea is to split
InArchiveRecovery into two variables, InArchiveRecov
Hi Amit,
Thank you for your careful review!
> -Original Message-
> From: Amit Kapila [mailto:amit.kap...@huawei.com]
> Sent: Friday, February 22, 2013 7:18 PM
> To: 'Etsuro Fujita'; 'pgsql-hackers'
> Subject: RE: [HACKERS] Review : Add hooks for pre- and post-processor
> executables for C
"David E. Wheeler" writes:
> While building 9.2.3 on OS X 10.8.2 today:
> checking ossp/uuid.h usability... no
> checking ossp/uuid.h presence... yes
> configure: WARNING: ossp/uuid.h: present but cannot be compiled
> configure: WARNING: ossp/uuid.h: check for missing prerequisite headers?
>
Michael Paquier writes:
> While testing a bit this feature, I noticed that use_remote_explain is
> available in the list of options for FOREIGN TABLE and SERVER but this is
> not specified in the docs:
> http://www.postgresql.org/docs/devel/static/postgres-fdw.html
Wups ... for some reason it's "
Andres Freund writes:
> On 2013-02-21 14:11:10 -0800, Kevin Grittner wrote:
>> DISABLE MATERIALIZED VIEW mv; -- ALTER clause for constraints
>> DISCARD MATERIALIZED VIEW DATA mv; -- session state
>> RELEASE MATERIALIZED VIEW DATA mv; -- savepoint
>> RESET MATERIALIZED VIEW DATA mv; -- run-time
31 matches
Mail list logo
