postgresql-9.1

I have the following table create table places(lat_lng point, place_name varchar(50)); insert into places values (POINT(-126.4, 45.32), 'Food Bar'); What should be the query to get all places close to particular lat/long? gis is installed. If you actually wanted to use PostGIS: create table places( lat_lng geography(Point,4326), place_name varchar(50) ); -- Two ways to make a geography point insert into places values (ST_MakePoint(-126.4, 45.32), 'Food Bar1'); insert into places values ('POINT(-126.4 45.32)', 'Food Bar2'); -- Spatial index create index places_lat_lng_idx on places using gist

I have a VM set up with Vagrant that has Postgres running on it (on port 5432), forwarded to port 8280 on the host machine. I have set the password for the default user and I can connect locally just fine. I have been trying to set up access from the host machine over port 8280, and I have been unable to get it working with 'MD5' as the trust method. I have set up postgresql.conf to listen on all addresses: # postgresql.conf listen_addresses = '*' and I have configured pg_hab.conf as follows: # pg_hab.conf #TYPE DATABASE USER CIDR-ADDRESS METHOD host all all 0.0.0.0/0 md5 With all of these

I have been migrating a MySQL db to Pg (9.1), and have been emulating MySQL ENUM data types by creating a new data type in Pg, and then using that as the column definition. My question -- could I, and would it be better to, use a CHECK CONSTRAINT instead? The MySQL ENUM types are implemented to enforce specific values entries in the rows. Could that be done with a CHECK CONSTRAINT? and, if yes, would it be better (or worse)? punkish Based on the comments and answers here, and some rudimentary research, I have the following summary to offer for comments from the Postgres-erati. Will really

I have a Postgres schema which looks like: The problem is that whenever I save text longer than 500 characters in the description column I get the error: value too long for type character varying(500) In the documentation for Postgres it says type text can have unlimited characters. I'm using postgresql-9.1. This table has been generated using Django 1.4 and the field type in the model is TextField, if that helps explain the problem further. Any ideas as why this is happening and what I can do to fix it? By specifying the column as VARCHAR(500) you've set an explicit 500 character limit. You

I have read from internet resources that a query will be slow when the offset increases. But in my case I think its too much slow. I am using postgres 9.3 Here is the query ( id is primary key): select * from test_table offset 3900000 limit 100; It returns me data in around 10 seconds . And I think its too much slow. I have around 4 million records in table. Overall size of the database is 23GB . Machine configuration: RAM: 12 GB CPU: 2.30 GHz Core: 10 Few values from postgresql.conf file which I have changed are as below. Others are default. shared_buffers = 2048MB temp_buffers = 512MB work

I'm having an issue selecting dates properly from Postgres - they are being stored in UTC, but not converting with the Date() function properly. Converting the timestamp to a date gives me the wrong date if it's past 4pm PST. 2012-06-21 should be 2012-06-20 in this case. The starts_at column datatype is timestamp without time zone . Here are my queries: Without converting to PST timezone: Select starts_at from schedules where id = 40; starts_at --------------------- 2012-06-21 01:00:00 Converting gives this: Select (starts_at at time zone 'pst') from schedules where id = 40; timezone ---------