On 10 August 2012 18:19, Fujii Masao wrote:
>> I've committed the simplified version for 9.2, as well as adding
>> support for streaming which you seem to have missed out.
>
> If the streaming case really must be covered, the fix should be backported to
> 9.1 and 9.0? Because there is the same "p
On Sat, Aug 04, 2012 at 12:11:56PM -0400, Tom Lane wrote:
> More generally, nobody is maintaining ecpg's copy of the datetime code,
> and that's been true for a very long time. I'm not personally
Well, maintaining as in fixing bugs I do as I find time. Maintaining as in
keeping in sync with the b
An EntpriseDB testing report indicated that pg_upgrade crashes if it
can't write into the current directory. This only happens in 9.2 and
head, so I have applied the attached patch to fix it.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterpri
Peter Eisentraut writes:
> What is the intended way to handle errors in the new logging hook?
I'm not sure there is anything very useful you can do to "handle" them,
if by "handle" you mean "report somewhere".
>From the point of view of elog.c, anything that might go wrong inside
a logging hook
CREATE OR REPLACE VIEW makes it possible to create views that have
circular dependencies, for instance:
regression=# create table tt(f1 int, f2 int);
CREATE TABLE
regression=# create view v1 as select * from tt;
CREATE VIEW
regression=# create view v2 as select * from v1;
CREATE VIEW
regression=#
On Sat, Jul 28, 2012 at 3:33 PM, Jeff Janes wrote:
> On Sat, Jul 7, 2012 at 9:17 PM, Satoshi Nagayasu wrote:
>> Hi,
>>
>> Jeff Janes has pointed out that my previous patch could hold
>> a number of the dirty writes only in single local backend, and
>> it could not hold all over the cluster, becau
On Sat, 2012-08-11 at 14:05 -0400, Tom Lane wrote:
> Peter Eisentraut writes:
> > What is the intended way to handle errors in the new logging hook?
>
> I'm not sure there is anything very useful you can do to "handle" them,
> if by "handle" you mean "report somewhere".
Yes, they ought to be wri
