Tag Info

Hot answers tagged

22

The line in your netstat report shows that the database is only listening on localhost:5432 (127.0.0.1) for incoming tcp connections. Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 3561/postgres So it can only accept local tcp connections regardless of what ...


15

Or, to retrieve all rows, just press the blue data grid. The tooltip "View data in the selected object" is almost making it too easy. Try the button with the funnel next to it to retrieve only a selection (for big tables).


12

I found this answer elsewhere. If your DB is on the local host, try leaving the host field blank in the connection as opposed to using “localhost” or “127.0.0.1″. This tells PgAdmin to connect via the local unix socket instead of TCP.


8

The short answer is "No". Temporary tables in other sessions are invisible by design. It makes no difference if two sessions have the same user. Even: The autovacuum daemon cannot access and therefore cannot vacuum or analyze temporary tables


8

We had the same problem 2 times on two different computer, in just a few days of interval. PgAdmin started to crash each time we open query builder. Restarting the computer, reinstalling pgAdmin with differents versions... Nothing resolved the problem. But we found the solution to this problem! PgAdmin uses a file where it saves the last queries (kind of ...


8

The lack of access to temporary tables in other sessions is not a matter of permissions, it's a technical limitation of the design. A PostgreSQL backend can't access temporary tables of another backend because none of the usual housekeeping to allow concurrent access is done for temporary tables. In 9.2 you will want to use an UNLOGGED table instead; this ...


7

Right click on the table and choose "View data" For a list of alternatives, check out the Postgres wiki: http://wiki.postgresql.org/wiki/Community_Guide_to_PostgreSQL_GUI_Tools


7

Under Windows this information is stored in the Registry under the key: HKEY_CURRENT_USER\Software\pgAdmin III In Linux systems I would expect some file in the user home directory.


6

You write: Each customer can have multiple sites, but only one should be displayed in this list. Yet, your query retrieves all rows. That would be a point to optimize. But you also do not define which site is to be picked. Either way, it does not matter much here. Your EXPLAIN shows only 5026 rows for the site scan (5018 for the customer scan). So ...


6

pgScript is a local script extension of pgAdmin, which you most probably do not want here. pgAdmin is a GUI, not a console application - there is no stdin you could easily use. If you need stdin to stream your content, use psql, which is a console application - with the \copy meta-command of psql. If you have a file (which you obviously do), just use SQL ...


5

pgadmin has it's own reverse-engineering functionality - it just examines the system tables like pg_class and pg_attribute to find the details. If what you're looking for is actually an easy way to show the CREATE statements for your objects that you can use from something else, you should look at pg_dump instead of pgadmin, it is much simpler. In ...


5

"I don't know how they got there in the first place" It could have happened as described here - although this generates an error on 8.4: If you create a table with any text type (i.e. text, varchar(10), etc.), then you can insert an invalid byte sequence into that field using octal escapes. For instance, if you have a UTF8-encoded database, ...


5

Digging around the internet, I've seen that this is a pretty common problem. The common solution is to use the plain text format dump and feed it through iconv to correct the encoding. Here is more information about that.


5

I can connect to my postgres instance from pgAdmin III without a password for any user including superusers such as postgres. Because you are connecting ok from another client, there is no reason you should not be able to connect from pgAdmin if they are on the same workstation - unless some firewall rule on the client itself is allowing one program but ...


5

Other than not using features that cause errors, no, there is no workaround. Since in this case one of the features that causes an error appears to be listing tablespaces during startup, you're out of luck. Just compile a newer version of PgAdmin-III from sources or use the command-line psql client that comes with PostgreSQL 9.2. PostgreSQL's system ...


5

This line: host all all 192.168.0.0/24 md5 will let through connections from IPs matching 192.168.0.X where X is any byte. The IP address of your error message being 192.168.108.161, it does not match this pattern because 108 is not 0. To enable addresses like 192.168.X.Y, you'd need a /16 instead of /24 meaning ...


5

lock_timeout is a new parameter that appeared with PostgreSQL 9.3 Per the release notes: Add configuration variable lock_timeout to allow limiting how long a session will wait to acquire any one lock (Zoltán Böszörményi) That would indicate that pgadmin is using a PostgreSQL 9.3 pg_dump command to take the backup, instead of 9.0. This is ...


5

There is a setting for that in the options: Max characters per column - useful when dealing with big columns. Obviously your setting is 256 characters. Set it higher or set it to -1 to disable the feature. Consult the fine manual here for more details.


5

In pgAdmin… To edit the postgresql.conf file:Choose Tools > Server Configuration > postgresql.conf To edit the pg_hba.conf file:Choose Tools > Server Configuration > pg_hba.conf Avoid the red-herring File menu: File > Open postgresql.conf File > Open pg_hba.conf


5

You could setup the ssh connection and tunnel outside pgAdmin and just let pgAdmin connect to the localport. On windows you could use putty for this on unixes you can use ssh If you use 15432 as localport then you can let pgAdmin connect to localhost with port 15432 and you leave the SSH tunnel option in pgAdmin OFF!


5

In Ubuntu 13.10 pgAdmin stores configuration in user's home directory: /home/<<username>>/.pgadmin3 or shorter ~/.pgadmin3 Note that this file is hidden, so you may need to enable some kind of "Show hidden files" option in your file manager.


5

I am adding 1k inserts by connection to the base, so I don't think it's related. I think it is related. You are probably adding exactly 1001 rows in each batch. All these numbers are multiples of 1001.


4

run: psql -U your_user_name your_db_name < your_dump_file


4

two options: Use the "datatype" SERIAL or create a sequence and use this sequence as a default value for your integer: CREATE SEQUENCE your_seq; CREATE TABLE foo( id int default nextval('your_seq'::regclass), other_column TEXT ); INSERT INTO foo(other_column) VALUES ('bar') RETURNING *;


4

You tell the COPY command to look for commas as delimiters (DELIMITERS ','), but there are no commas in your CSV. Use the 'text' format instead (it's the default, so you don't have to specify it) and do not specify a delimiter: The default is a tab character in text format. (source)


4

When a cursor is defined at the SQL level with DECLARE, there is an option WITH HOLD that makes it continue to exist after commiting the current transaction. Quoting the doc: WITH HOLD specifies that the cursor can continue to be used after the transaction that created it successfully commits On the other hand, a refcursor opened by a plpgsql ...


4

Obviously, your client (Windows) is running on a different machine than your server (Ubuntu). You cannot read the remote file system. Inspecting the logs only works if your client is on the same machine (or has access to the remote file system by way of some advanced trickery.) To suppress the error message remove the log file from the display. In the ...


4

I'm assuming that you want to create this extension in another server. I'm guessing that the server didn't get the "postgresql contrib" package installed. This package contains the "standard" extensions that are available from the PostgreSQL source code. I think you need to get the system administrator to install the required package for your OS. For ...


4

The sequences are designed like that, the are not supposed to produce contiguous numbers. However, you can reset them before (re)trying the COPY with SELECT setval('sequence_name', (SELECT max(id) FROM your_table));


4

What could explain why this gets created? You created the index. Or the client software you are working with did it for you. Postgres certainly didn't. Do I still need to create another index on my product column to improve performance of queries on it? No. A second index on the same column would be a total waste. It's not even certain the first ...



Only top voted, non community-wiki answers of a minimum length are eligible