pgsql-hackers since 2010-02-21 00:00
The PostgreSQL developers team lives here. Discussion of current development issues, problems and bugs, and proposed new features. If your question cannot be answered by people in the other lists, and it is likely that only a developer will know the answer, you may re-post your question in this list. You must try elsewhere first!
Search the Archives
Browse Archives
Prev
|
Next
Feb. 21, 2010
Thread |
Author |
Time |
Re: scheduler in core
|
Jaime Casanova |
00:03 |
Re: alpha4 bundled -- please verify
|
Josh Berkus |
00:08 |
Re: scheduler in core
|
Dave Page |
00:32 |
Re: scheduler in core
|
Dave Page |
00:34 |
Re: PGXS: REGRESS_OPTS=--load-language=plpgsql
|
David E. Wheeler |
00:37 |
Re: scheduler in core
|
Jaime Casanova |
00:38 |
Re: scheduler in core
|
Dave Page |
00:40 |
Re: scheduler in core
|
Andrew Dunstan |
00:40 |
Re: scheduler in core
|
Dave Page |
00:44 |
Re: PGXS: REGRESS_OPTS=--load-language=plpgsql
|
Tom Lane |
00:59 |
Re: scheduler in core
|
Joshua D. Drake |
01:06 |
Re: PGXS: REGRESS_OPTS=--load-language=plpgsql
|
Bruce Momjian |
01:11 |
Re: scheduler in core
|
Robert Haas |
01:50 |
Re: scheduler in core
|
Jaime Casanova |
01:50 |
Re: parallelizing subplan execution (was: explain and PARAM_EXEC)
|
Robert Haas |
03:25 |
Re: PGXS: REGRESS_OPTS=--load-language=plpgsql
|
Robert Haas |
03:38 |
Re: PGXS: REGRESS_OPTS=--load-language=plpgsql
|
Tom Lane |
03:56 |
Re: PGXS: REGRESS_OPTS=--load-language=plpgsql
|
Robert Haas |
04:08 |
Re: parallelizing subplan execution
|
Mark Kirkwood |
07:37 |
Re: scheduler in core
|
Pavel Stehule |
07:44 |
Re: scheduler in core
|
Dimitri Fontaine |
08:24 |
Re: scheduler in core
|
Dimitri Fontaine |
08:47 |
Re: parallelizing subplan execution
|
Dimitri Fontaine |
09:38 |
Plans for 9.1, Grouping Sets, disabling multiqueries, contrib module for string, plpgpsm, preload dictionaries
|
Pavel Stehule |
10:00 |
getting to beta
|
Robert Haas |
11:43 |
Re: Avoiding bad prepared-statement plans.
|
Robert Haas |
12:37 |
Re: parallelizing subplan execution (was: explain and PARAM_EXEC)
|
Greg Stark |
12:57 |
Re: scheduler in core
|
Andrew Dunstan |
13:46 |
Re: Plans for 9.1, Grouping Sets, disabling multiqueries, contrib module for string, plpgpsm, preload dictionaries
|
Tom Lane |
14:23 |
Re: getting to beta
|
Tom Lane |
14:26 |
Re: scheduler in core
|
Bruce Momjian |
15:12 |
Re: getting to beta
|
Bruce Momjian |
15:15 |
Re: scheduler in core
|
Lucas |
15:17 |
Re: scheduler in core
|
Ron Mayer |
17:04 |
Re: PGXS: REGRESS_OPTS=--load-language=plpgsql 📎
|
Tom Lane |
17:29 |
Re: scheduler in core
|
Tom Lane |
17:33 |
some issue in plpgsq - exec code?
|
Pavel Stehule |
17:35 |
Re: getting to beta
|
Robert Haas |
17:50 |
WAL-support for Pluggable Indexes
|
Simon Riggs |
17:54 |
Re: scheduler in core
|
Robert Haas |
17:54 |
Re: getting to beta
|
Stefan Kaltenbrunner |
17:58 |
Re: scheduler in core
|
Robert Haas |
17:58 |
Re: scheduler in core
|
Tom Lane |
18:05 |
Re: PGXS: REGRESS_OPTS=--load-language=plpgsql
|
Robert Haas |
18:09 |
Re: scheduler in core
|
Simon Riggs |
18:11 |
Re: scheduler in core
|
Robert Haas |
18:13 |
Re: scheduler in core
|
Robert Haas |
18:13 |
Re: WAL-support for Pluggable Indexes
|
Tom Lane |
18:14 |
Re: WAL-support for Pluggable Indexes
|
Robert Haas |
18:20 |
Re: PGXS: REGRESS_OPTS=--load-language=plpgsql
|
Tom Lane |
18:21 |
Re: PGXS: REGRESS_OPTS=--load-language=plpgsql
|
Robert Haas |
18:40 |
A thought on Index Organized Tables
|
Gokulakannan Somasundaram |
19:11 |
Re: PGXS: REGRESS_OPTS=--load-language=plpgsql
|
Bruce Momjian |
19:25 |
Re: scheduler in core
|
Dimitri Fontaine |
19:46 |
Re: PGXS: REGRESS_OPTS=--load-language=plpgsql
|
Tom Lane |
22:11 |
Re: PGXS: REGRESS_OPTS=--load-language=plpgsql
|
Tom Lane |
22:16 |
Re: pgsql: Speed up CREATE DATABASE by deferring the fsyncs until after
|
Andres Freund |
23:43 |
Feb. 22, 2010
Thread |
Author |
Time |
pgsql: Oops, don't forget to rewind the directory before scanning it to
|
Greg Stark |
00:11 |
Re: pgsql: Speed up CREATE DATABASE by deferring the fsyncs until after
|
Greg Stark |
00:11 |
Re: PGXS: REGRESS_OPTS=--load-language=plpgsql
|
Bruce Momjian |
00:23 |
Re: PGXS: REGRESS_OPTS=--load-language=plpgsql
|
David Fetter |
02:06 |
Re: pgsql: Oops, don't forget to rewind the directory before scanning it to
|
Tom Lane |
02:30 |
Re: pgsql: Oops, don't forget to rewind the directory before scanning it to
|
Fujii Masao |
02:38 |
Re: pgsql: Speed up CREATE DATABASE by deferring the fsyncs until after
|
Tom Lane |
02:54 |
Time travel on the buildfarm
|
Tom Lane |
03:28 |
Re: [COMMITTERS] pgsql: Oops, don't forget to rewind the directory before scanning it to
|
Tom Lane |
03:58 |
Re: Streaming replication on win32, still broken
|
Fujii Masao |
04:47 |
Re: A thought on Index Organized Tables
|
Heikki Linnakangas |
06:51 |
Re: [COMMITTERS] pgsql: Oops, don't forget to rewind the directory before scanning it to
|
Andres Freund |
07:59 |
Re: A thought on Index Organized Tables
|
Gokulakannan Somasundaram |
08:18 |
Re: scheduler in core
|
Simon Riggs |
09:17 |
Re: pgsql: Speed up CREATE DATABASE by deferring the fsyncs until after
|
Greg Stark |
10:15 |
Re: A thought on Index Organized Tables
|
Greg Stark |
10:29 |
Re: A thought on Index Organized Tables
|
Gokulakannan Somasundaram |
11:01 |
pgsql: Move documentation of all recovery.conf option to a new chapter.
|
Heikki Linnakangas |
11:47 |
Re: Streaming replication and pg_xlogfile_name()
|
Heikki Linnakangas |
12:30 |
Re: Time travel on the buildfarm
|
Andrew Dunstan |
14:03 |
Re: A thought on Index Organized Tables
|
Alvaro Herrera |
14:38 |
Re: Plans for 9.1, Grouping Sets, disabling multiqueries, contrib module for string, plpgpsm, preload dictionaries
|
Alvaro Herrera |
14:42 |
ALTER TABLE documentation
|
Robert Haas |
14:46 |
Re: Re: pgsql: Speed up CREATE DATABASE by deferring the fsyncs until after
|
Tom Lane |
14:53 |
Re: Plans for 9.1, Grouping Sets, disabling multiqueries, contrib module for string, plpgpsm, preload dictionaries
|
Pavel Stehule |
15:31 |
Re: ALTER TABLE SET STATISTICS requires
AccessExclusiveLock
|
Bruce Momjian |
15:32 |
Re: [COMMITTERS] Re: pgsql: Speed up CREATE DATABASE by deferring the fsyncs until after
|
Tom Lane |
15:42 |
Re: Recent vendor SSL renegotiation patches break PostgreSQL
|
Magnus Hagander |
16:42 |
Re: Recent vendor SSL renegotiation patches break PostgreSQL
|
Tom Lane |
16:54 |
Re: Recent vendor SSL renegotiation patches break PostgreSQL
|
Magnus Hagander |
17:00 |
Re: Recent vendor SSL renegotiation patches break PostgreSQL
|
Tom Lane |
17:25 |
Reason why set-value functions not allowed in GREATEST(), etc?
|
Hitoshi Harada |
17:25 |
Re: Recent vendor SSL renegotiation patches break PostgreSQL
|
Chris Campbell |
17:31 |
Re: Recent vendor SSL renegotiation patches break PostgreSQL
|
Joshua D. Drake |
17:32 |
Re: scheduler in core
|
Jaime Casanova |
17:34 |
Re: Recent vendor SSL renegotiation patches break PostgreSQL
|
Joshua D. Drake |
17:35 |
Re: Recent vendor SSL renegotiation patches break PostgreSQL
|
Magnus Hagander |
17:45 |
Re: What does this configure warning mean? 📎
|
Bruce Momjian |
18:01 |
Re: transaction_isolation vs.
default_transaction_isolation
|
Bruce Momjian |
18:08 |
Re: Wire protocol docs
|
Bruce Momjian |
18:12 |
Re: What does this configure warning mean?
|
Alvaro Herrera |
18:13 |
Re: What does this configure warning mean?
|
Bruce Momjian |
18:14 |
Re: Reason why set-value functions not allowed in GREATEST(), etc?
|
Pavel Stehule |
18:16 |
Re: scheduler in core
|
Heikki Linnakangas |
18:18 |
Re: scheduler in core
|
Pavel Stehule |
18:22 |
tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)
|
Jaime Casanova |
18:34 |
Re: scheduler in core
|
Merlin Moncure |
18:42 |
Re: Recent vendor SSL renegotiation patches break
PostgreSQL
|
Joshua D. Drake |
18:49 |
Re: tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)
|
Heikki Linnakangas |
18:50 |
Re: tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)
|
Jaime Casanova |
18:59 |
Re: Recent vendor SSL renegotiation patches break PostgreSQL
|
Dave Page |
19:00 |
Re: What does this configure warning mean?
|
Alvaro Herrera |
19:00 |
Re: scheduler in core
|
Alvaro Herrera |
19:29 |
Re: Recent vendor SSL renegotiation patches break PostgreSQL
|
Magnus Hagander |
19:34 |
Re: Recent vendor SSL renegotiation patches break PostgreSQL
|
Magnus Hagander |
19:39 |
Re: What does this configure warning mean?
|
Bruce Momjian |
19:48 |
Re: tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)
|
Tom Lane |
19:53 |
Re: Recent vendor SSL renegotiation patches break PostgreSQL
|
Tom Lane |
19:57 |
Re: tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)
|
Jaime Casanova |
20:08 |
Re: tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)
|
Jaime Casanova |
20:10 |
Re: scheduler in core
|
Merlin Moncure |
20:15 |
Re: Reason why set-value functions not allowed in GREATEST(), etc?
|
Tom Lane |
20:24 |
Re: What does this configure warning mean?
|
Tom Lane |
20:30 |
Re: What does this configure warning mean?
|
Bruce Momjian |
20:33 |
Re: What does this configure warning mean?
|
Bruce Momjian |
20:33 |
Re: What does this configure warning mean?
|
Tom Lane |
21:08 |
Re: What does this configure warning mean?
|
Bruce Momjian |
21:17 |
Re: tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)
|
Dimitri Fontaine |
21:18 |
Re: tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)
|
Merlin Moncure |
21:35 |
Re: tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)
|
Tom Lane |
21:37 |
Re: tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)
|
Dimitri Fontaine |
21:53 |
Re: tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)
|
Jaime Casanova |
23:22 |
Re: tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)
|
David Christensen |
23:41 |
Re: remove useless set of active snap
|
Bruce Momjian |
23:47 |
Re: commented out para in docs
|
Bruce Momjian |
23:51 |
Feb. 23, 2010
Browse Archives
Prev
|
Next