I suggest you ...

In-memory table

Table placed only in RAM, visibility for all

364 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Antony PetropavlovskiyAntony Petropavlovskiy shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    4 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Nathan ClaytonNathan Clayton commented  ·   ·  Flag as inappropriate

        What would be really nice would be a table hint to indicate that it should be loaded into memory and kept there once the system loads up without having to create and execute any queries to do so. This would be ideal for dimension tables that are frequently accessed (e.g. date/time dimensions), but you didn't necessarily want to loose upon system shutdown. Maybe another hint to indicate that the table is to be memory-only and not saved to disk.

        Something like `create table ... with inmemory` and `create table ... with inmemory nodisk`

      • Darren DuncanDarren Duncan commented  ·   ·  Flag as inappropriate

        It should be possible to do this both with private table variables and public/shared ones. On the other hand, if Postgres provides the ability to selectively say that some tables are not logged and otherwise hint that they are small or should be kept in RAM where possible, that should meet the goal, perhaps.

      Feedback and Knowledge Base