New answers tagged

1

If You are querying just one table (like SELECT * FROM table) then right click on it in Object browser, choose View Data from context menu, You will have options to View Top 100 Rows or View Last 100 Rows. Other than that, use LIMIT and OFFSET clauses in Your queries: https://www.postgresql.org/docs/9.3/static/queries-limit.html


1

Using pgAdmin III, I ran the following command to generate 100,000 random records. create table t_random as select s, md5(random()::text) from generate_Series(1, 100000) s; I then did as MarcinS suggested in his answer: "right click on it in Object browser, choose View Data from context menu, You will have options to View Top 100 Rows or View Last 100 ...


0

You should never stop a vacuum process, ever. A vacuum full will completely recreate the table, so it should take roughly as long to run as it would to create and populate a brand new table and index it with all 490_000_000 records.


0

PgAdmin is just a tool to work on existing database. @FabrizioMazzoni is right - you have to install PostgreSQL server first, and the you can use PgAdmin to work on it. New Server Registration is a form to connect to an existing database server, not to create one.


0

I seems that it's a known bug. I'm answering to my own question with this workaround. If you use PostgreSQL 9.4+, one workaround is to use REFRESH MATERIALIZED VIEW CONCURRENTLY. From PostgreSQL's manual: CONCURRENTLY Refresh the materialized view without locking out concurrent selects on the materialized view. Without this option a refresh which ...


1

You can restore all affected tables into a different schema, there are a variety of ways in which you can do that (several good ideas in http://stackoverflow.com/questions/4191653/i-want-to-restore-the-database-with-a-different-schema). Once the table is in a separate schema, you can compare them by primary key, and insert the missing ones, like so for each ...


0

This answer was perfect! I found that the service was running under the Windows user postgres, so I went into that user's app data folder to the file (C:\Users\postgres\AppData\Roaming\postgresql\pgpass.conf), right-clicked and edited it with Notepad++, and added the line: localhost:5432:CPLit_Tables:postgres:**** AND that was all that was needed to get ...



Top 50 recent answers are included