Arnau wrote:
Hi Thor,
Thor-Michael Støre wrote:
On 2007-04-04 Arnau wrote:
Josh Berkus wrote:
Arnau,
Is there anything similar in PostgreSQL? The idea behind this
is how I can do in PostgreSQL to have tables where I can query
on them very often something like every few seconds and get
On Wednesday 04 April 2007 07:51, Arnau wrote:
Hi Ansgar ,
On 2007-04-04 Arnau wrote:
Josh Berkus wrote:
Is there anything similar in PostgreSQL? The idea behind this is how
I can do in PostgreSQL to have tables where I can query on them very
often something like every few seconds and
Dimitri,
Probably another helpful solution may be to implement:
ALTER TABLE LOGGING OFF/ON;
just to disable/enable WAL?
Actually, a patch similar to this is currently in the queue for 8.3.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of
Wow, it's excellent! :))
probably the next step is:
ALTER TABLE CACHE ON/OFF;
just to force keeping any table in the cache. What do you think?...
Rgds,
-Dimitri
On 4/5/07, Josh Berkus josh@agliodbs.com wrote:
Dimitri,
Probably another helpful solution may be to implement:
ALTER
Hi Josh,
Josh Berkus wrote:
Arnau,
Is there anything similar in PostgreSQL? The idea behind this is how I
can do in PostgreSQL to have tables where I can query on them very often
something like every few seconds and get results very fast without
overloading the postmaster.
If you're only
On 2007-04-04 Arnau wrote:
Josh Berkus wrote:
Is there anything similar in PostgreSQL? The idea behind this is how
I can do in PostgreSQL to have tables where I can query on them very
often something like every few seconds and get results very fast
without overloading the postmaster.
If
Hi Ansgar ,
On 2007-04-04 Arnau wrote:
Josh Berkus wrote:
Is there anything similar in PostgreSQL? The idea behind this is how
I can do in PostgreSQL to have tables where I can query on them very
often something like every few seconds and get results very fast
without overloading the
Hi Thor,
Thor-Michael Støre wrote:
On 2007-04-04 Arnau wrote:
Josh Berkus wrote:
Arnau,
Is there anything similar in PostgreSQL? The idea behind this
is how I can do in PostgreSQL to have tables where I can query
on them very often something like every few seconds and get
results very fast
Probably another helpful solution may be to implement:
ALTER TABLE LOGGING OFF/ON;
just to disable/enable WAL?
First it may help in all cases of intensive data load while you slow
down other sessions with increasing WAL activity.
Then you have a way to implement MEMORY-like tables on RAM
Hi all,
In MySQL when you create a table you can define something like:
CREATE TABLE `sneakers` (
`sneaker_id` char(24) NOT NULL,
`sneaker_time` int(10) unsigned NOT NULL default '0',
`sneaker_user` int(10) unsigned NOT NULL default '0',
UNIQUE KEY `sneaker_id` (`sneaker_id`)
)
Arnau,
Is there anything similar in PostgreSQL? The idea behind this is how I
can do in PostgreSQL to have tables where I can query on them very often
something like every few seconds and get results very fast without
overloading the postmaster.
If you're only querying the tables every few
Arnau [EMAIL PROTECTED] writes:
MySQL manual says:
The MEMORY storage engine creates tables with contents that are stored
in memory. As indicated by the name, MEMORY tables are stored in memory.
Is there anything similar in PostgreSQL?
As long as you have shared_buffers large enough (or
Indeed... I looked through the official TODO list and was unable to
find an entry for global temporary tables- such a thing would be
ideal for any transient data such as web sessions or materialized
views. Is there any reason why global temp tables shouldn't be
implemented? (And, no, I'm
A.M. wrote:
Indeed... I looked through the official TODO list and was unable to
find an entry for global temporary tables- such a thing would be ideal
for any transient data such as web sessions or materialized views. Is
there any reason why global temp tables shouldn't be implemented?
(And,
On Apr 3, 2007, at 15:39 , C. Bergström wrote:
A.M. wrote:
Indeed... I looked through the official TODO list and was unable
to find an entry for global temporary tables- such a thing would
be ideal for any transient data such as web sessions or
materialized views. Is there any reason why
On Tuesday 03 April 2007 12:47, A.M. [EMAIL PROTECTED] wrote:
On Apr 3, 2007, at 15:39 , C. Bergström wrote:
I would like to use transactional semantics over tables that can
disappear whenever the server fails. memcached does not offer that.
How would temporary tables?
--
Ginsberg's Theorem:
On Apr 3, 2007, at 16:00 , Alan Hodgson wrote:
On Tuesday 03 April 2007 12:47, A.M.
[EMAIL PROTECTED] wrote:
On Apr 3, 2007, at 15:39 , C. Bergström wrote:
I would like to use transactional semantics over tables that can
disappear whenever the server fails. memcached does not offer that.
17 matches
Mail list logo
