POSTGRESQL BUG REPORT
Your name : Takuya Koide
Your email address : koide-txa (at) necst (dot) nec
I'm sorry Tom, you are right.
Atentamente,
Soluciones Integrales GIS C.A (SIGIS)
Christian Gonzalez
[EMAIL PROTECTED]
-Mensaje original-
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
En nombre de Tom Lane
Enviado el: Miércoles, 18 de Abril de 2007 01:24 p.m.
Para: Christian Gonzalez
takuya koide wrote:
> 4) send 'SIGSTOP' signal to postgres
> # kill -SIGSTOP 3619
> # ps axuw|grep -i postgres|grep -Ev 'grep|bash|su -'
> postgres 3507 0.0 1.1 21352 2804 ?S18:48 0:00
> /usr/bin/postmaster -p 5432 -D /var/lib/pgsql/data
> postgres 3509 0.0 0.2 11132 568
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> takuya koide wrote:
>> 4) send 'SIGSTOP' signal to postgres
> If you "stop" a process by SIGSTOP you must make it run again with
> SIGCONT. Otherwise it's just not processing signals, so it'll obviously
> not shut down. I don't think this is a bug.
S
pg_dump -O apparently removes all instances of ALTER TABLE ... OWNER TO
from the output, but does not remove ALTER SEQUENCE ... OWNED BY from
the output.
Specifically this is with SERIAL sequences, which are dumped using the
ALTER SEQUENCE syntax (as of 8.2). Normal sequences are dumped using the
On Wed, 2007-04-25 at 11:36 -0700, Jeff Davis wrote:
> pg_dump -O apparently removes all instances of ALTER TABLE ... OWNER TO
> from the output, but does not remove ALTER SEQUENCE ... OWNED BY from
> the output.
>
> Specifically this is with SERIAL sequences, which are dumped using the
> ALTER SE
I wrote:
> Heikki Linnakangas <[EMAIL PROTECTED]> writes:
>> We could have two kinds of seq scans, with and without support for
>> concurrent inserts.
> Yeah, I considered that too, but it just seems too error-prone. We
> could maybe make it trustworthy by having hash_seq_search complain if
> it
>>> On Wed, Apr 25, 2007 at 12:42 AM, in message <[EMAIL PROTECTED]>,
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Lee Chua" <[EMAIL PROTECTED]> writes:
>> When we select and order by time we get 00:00:00 as the latest time of the
>> day.
>
> Really? It works as expected for me:
>
> regression=# crea
Jeff Davis <[EMAIL PROTECTED]> writes:
> pg_dump -O apparently removes all instances of ALTER TABLE ... OWNER TO
> from the output, but does not remove ALTER SEQUENCE ... OWNED BY from
> the output.
Why should it? That's not ownership in the same sense.
regards, tom lane
On Wed, 2007-04-25 at 16:44 -0400, Tom Lane wrote:
> Jeff Davis <[EMAIL PROTECTED]> writes:
> > pg_dump -O apparently removes all instances of ALTER TABLE ... OWNER TO
> > from the output, but does not remove ALTER SEQUENCE ... OWNED BY from
> > the output.
>
> Why should it? That's not ownership
Tom Lane wrote:
I wrote:
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
We could have two kinds of seq scans, with and without support for
concurrent inserts.
Yeah, I considered that too, but it just seems too error-prone. We
could maybe make it trustworthy by having hash_seq_search complai
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I still don't want to introduce more checking overhead into
>> hash_seq_search, though, so what I'm now thinking about is a new
>> dynahash primitive named something like "hash_freeze", which'd mark a
>> hashtable as disallowing in
Thank you for your reply.
On Wed, 25 Apr 2007 09:44:47 -0400
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> takuya koide wrote:
>
> > 4) send 'SIGSTOP' signal to postgres
> > # kill -SIGSTOP 3619
> > # ps axuw|grep -i postgres|grep -Ev 'grep|bash|su -'
> > postgres 3507 0.0 1.1 21352 2804 ?
Thank you for your reply.
On Wed, 25 Apr 2007 10:22:25 -0400
Tom Lane <[EMAIL PROTECTED]> wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > takuya koide wrote:
> >> 4) send 'SIGSTOP' signal to postgres
>
> > If you "stop" a process by SIGSTOP you must make it run again with
> > SIGCONT. O
14 matches
Mail list logo
