Hi Chan,
I think this is configuration issue.
This issue is happening because log files will always append when
server is restarted. What I can see from your configuration,
log_rotation_age=1d (1 day) which is greater than daily schedule
shutdown/restart time. So this is the reaso
Rikard Pavelic wrote:
> The only inconsistent thing is check constraint, which behaves as
> NOT column IS NULL instead of column IS NOT NULL as docs says.
So currently a NOT NULL constraint on a column with a composite type
is equivalent to:
CHECK (NOT c IS NULL)
and the question is whethe
"Kevin Grittner" writes:
> Rikard Pavelic wrote:
>> The only inconsistent thing is check constraint, which behaves as
>> NOT column IS NULL instead of column IS NOT NULL as docs says.
> So currently a NOT NULL constraint on a column with a composite type
> is equivalent to:
> CHECK (NOT c IS NU
I have exactly same issue described in Bug #6201:
Bug reference: 6201
Logged by: Jerome Schulteis
Email address: jerome(dot)schulteis(at)edstrom(dot)com
PostgreSQL version: 9.0.4
Operating system: Windows XP Pro SP3
Description:Windows User Log Off Causes Backend Excep
Tom Lane wrote:
> "Kevin Grittner" writes:
>> So currently a NOT NULL constraint on a column with a composite
>> type is equivalent to:
>> CHECK (NOT c IS NULL)
>
> I don't believe this statement is accurate. What's really
> happening is that a column-not-null constraint is a
> datatype-indep
"Kevin Grittner" writes:
> Tom Lane wrote:
>> It's not clear to me whether the SQL standard rules on what should
>> happen in this case, or whether we should listen to it if it does
>> say that these values are not distinct. They certainly *look*
>> distinct.
> I do sympathize with the point o
Tom Lane wrote:
> The reason I mentioned arrays is that it seems clear to me that
> nobody sane would consider ARRAY[NULL,NULL]::int[] to be
> equivalent to NULL::int[].
I will defer on that to anyone who has been in a position where the
former has any meaningful semantics in a SQL environment
Heikki Linnakangas writes:
> This test case can be further reduced into:
> explain analyze
> SELECT * FROM generate_series(1,10) i
> WHERE (SELECT array(select repeat('a', 1) || i) u1) is not null;
> We're leaking the array constructed on each row, in ExecSetParamPlan().
> At line 1000
