On Sat, Feb 28, 2015 at 3:39 PM, inspector morse inspectormors...@gmail.com
wrote:
Is it a good idea to write a simple application (consisting of just data
entry interfaces) in pure pgsql?
Basically, we would have each page has a stored function in postgresql
that is called by php+apache
On Wed, Feb 18, 2015 at 5:48 AM, Brian Sutherland br...@vanguardistas.net
wrote:
# dump and reload
pg_dump --username super --format c -f dump.dump orig
createdb copied
It might be helpful to dump in the plain SQL format and look at what it's
doing.
On Sun, Feb 8, 2015 at 2:20 PM, Oliver ofab...@gmail.com wrote:
If I want change postgresql encoding, I have understood that I should
reinstall postgresql (I do installation from rpm official binary files for
red hat)
I can't answer your question about whether the encodings need to be the
On Tue, Feb 3, 2015 at 11:28 PM, Sam Saffron sam.saff...@gmail.com wrote:
Note: I still consider this a bug/missing feature of sorts since the
planner could do better here, and there is no real clean way of
structuring a query to perform efficiently here, which is why I
erroneously cross
On Tue, Feb 3, 2015 at 9:33 PM, BladeOfLight16 bladeofligh...@gmail.com
wrote:
This is why ORMs are bad. They make hard problems *much* harder, and the
only benefit is that they maybe make easy problems a little quicker. The
cost/savings is *heavily* skewed toward the cost, since there's
On Mon, Feb 2, 2015 at 1:16 AM, Sam Saffron sam.saff...@gmail.com wrote:
However, the contortions on the above query make it very un-ORM
friendly as I would need to define a view for it but would have no
clean way to pass limits and offsets in.
This is why ORMs are bad. They make hard
BEGIN
EXECUTE IMMEDIATE 'DROP TABLE CONTAINER';
EXCEPTION
WHEN OTHERS THEN
IF SQLCODE != -942 THEN
RAISE;
END IF;
END;
Jim nailed it. In PostgreSQL, this is just
DROP TABLE IF EXISTS CONTAINER;
One line. No dynamic SQL, exception block, or even a block
Have you considered normalizing?
Here's a SQLFiddle example: http://sqlfiddle.com/#!15/61897/3/0. It uses
text instead of citext, but I imagine your results should be similar. Also,
I think usage of citext is generally recommended against.
The basic idea is to not use an array but use a second
On Fri, Nov 1, 2013 at 9:29 AM, Birta Levente blevi.li...@gmail.com wrote:
I don't know what is this geoserver, but this port 8080 I think it's not
relevant in this.
I might be able to help: http://geoserver.org/display/GEOS/Welcome.
GeoServer is a Java web application that retrieves GIS data
On Tue, Oct 22, 2013 at 1:20 AM, James Sewell james.sew...@lisasoft.comwrote:
That looks great, but it doesn't really help with my problem unless I'm
missing something (very possible!)
I need a way to backup either from SQL in PSQL (possibly \!) or from a
PG/PLSQL function to a file with a
On Tue, Oct 22, 2013 at 3:15 PM, Moshe Jacobson mo...@neadwerx.com wrote:
Here is the full code. It is not “minimal”, but actually what we are using.
fn_get_create_or_update_space_sku() will create a non-existent row, or
update it with the passed-in data if it already exists.
You’ll notice
I've only skimmed this thread, but clearly, this is why using functions
with side effects in the middle of complex queries is a bad idea. =)
Something like SELECT func_with_side_effect(1); is probably fine, but
beyond that, put the function in the middle of a DO block or something and
actually
On Mon, Oct 21, 2013 at 6:52 PM, BladeOfLight16 bladeofligh...@gmail.comwrote:
In my opinion, the simplest and most correct way to handle this is to
document that there are no guarantees about what will happen with volatile
functions in these strange cases. PostgreSQL shouldn't have to make
On Fri, Oct 11, 2013 at 9:32 AM, Jesse Long j...@unknown.za.net wrote:
explain select * from archive_document_index where node_id = 29 and value
= 'BSH70002152';
QUERY PLAN
--**--**
On Mon, Sep 9, 2013 at 8:12 AM, Marc Mamin m.ma...@intershop.de wrote:
hi,
in addition to the others comments, you can also remove ELSE 0 from
your query.
It will result in NULL values that are discarded by SUM.
For that matter, you could clean this up by using COUNT as your
On Fri, Sep 6, 2013 at 1:58 PM, David Kerr d...@mr-paradox.net wrote:
I suspect this feature makes more sense on a windows platform. On linux
where we can
go psql -f ${SQLPATH}/file.sql . it becomes less pressing. Even Oracle
on unix/linux where you can go sqlplus EOD @${SQLPATH}/file.sql
On Tue, Aug 27, 2013 at 9:24 AM, superzhangfei superzhang...@aliyun.comwrote:
When the package be excused,an error occured.
Hello. First, can you reproduce the error without the PACKAGE? As in just
CREATE TYPE and CREATE PROCEDURE statements? If so, what are the errors?
And I think you mean
On Mon, Aug 26, 2013 at 3:17 AM, gajendra s v svgajen...@gmail.com wrote:
Please explain me why it is ?
A good place to start would be removing all the parts here that don't seem
to matter. Your problem seems to be with the recursive query (since that is
the part you're changing). Cut off
On Sun, Aug 25, 2013 at 5:59 PM, Janek Sendrowski jane...@web.de wrote:
SELECT v_rec1.user,
sum(CASE WHEN v_rec_fts.lev BETWEEN 0 AND 25 THEN 1 ELSE 0 END) as
0 to 25,
sum(CASE WHEN v_rec_fts.lev BETWEEN 25 AND 50 THEN 1 ELSE 0 END)
as 25 to 50,
sum(CASE WHEN
On Sun, Aug 25, 2013 at 8:36 PM, BladeOfLight16 bladeofligh...@gmail.comwrote:
This appears to be some kind of equal interval problem.
SELECT v_rec1.user,
WIDTH_BUCKET(v_rec_fts.lev, 0, 100, 4) AS bucket
COUNT(*) as count,
FROM v_rec2
GROUP BY user, bucket;
(Untested
On Thu, Aug 22, 2013 at 6:36 PM, Ian Lawrence Barwick barw...@gmail.comwrote:
INSERT INTO t (t_field1, t_field2, t_field3)
SELECT r.field1, r.field2, (x+y)
FROM r
Obligatory link to documentation:
http://www.postgresql.org/docs/9.2/static/sql-insert.html. See where it
says [ (
On Mon, Aug 19, 2013 at 4:27 AM, Vik Fearing vik.fear...@dalibo.com wrote:
Yes, I would use a trigger for this.
snip
This is definitely the right answer, but keep in mind that this will slow
down your inserts since it calls slow_function for each insert. Make sure
you can afford that
On Wed, Aug 14, 2013 at 2:56 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Our interpretation is that a bare column name (ORDER BY foo) is resolved
first as an output-column label, or failing that as an input-column name.
However, as soon as you embed a name in an expression, it will be treated
On Wed, Aug 7, 2013 at 4:43 AM, Luca Ferrari fluca1...@infinito.it wrote:
Not really helpful, but here are my considerations.
The low frequency and the preference for a single server suggest me a
dump and restore cycle on two databases, assuming this is possible due
to not high volume data.
The company I work for has a client who has expressed interest in having a
staging database for their data. Staging as in they add data, do some
QCing, then push to a database with an identical schema to make it public.
Fortunately, we're not doing that right now, but it's something they may
want
On Mon, Aug 5, 2013 at 2:21 AM, Thomas Kellerer spam_ea...@gmx.net wrote:
Stephen Brearley, 02.08.2013 11:40:
Why don't you use the official way to re-configure the Windows service and
use pg_ctl unregister and pg_ctl register
to make it use the correct data directory. There is no need to
On Sat, Aug 3, 2013 at 7:16 AM, Alban Hertroys haram...@gmail.com wrote:
They are cluster specific, as the roles are stored in the database. If you
switch between different data directories, that means you're switching the
available roles as well. And their details, such as passwords. You're
On Thu, Aug 1, 2013 at 8:15 PM, Adrian Klaver adrian.kla...@gmail.comwrote:
What you want is a default that only works during ALTER ADD COLUMN. At
that point though, there is no data added and DEFAULT only works with
INSERTS. Your example of USING with ALTER data_type works because there
On Fri, Jul 26, 2013 at 6:28 PM, Tom Lane t...@sss.pgh.pa.us wrote:
snip
I think we could do with both more documentation, and better error
messages for these cases. In the SET-where-you-should-use-ADD case,
perhaps
ERROR: option use_remote_estimate has not been set
HINT: Use ADD not
On Fri, Aug 2, 2013 at 10:18 AM, Adrian Klaver adrian.kla...@gmail.comwrote:
You can't do that and have it work. \base is just part of the puzzle, you
need the complete \data directory for Postgres to work.
The problem(as stated before) is you have two distinct installations of
the Postgres
When I want to add a new column with a NOT NULL constraint, I need to
specify a DEFAULT to avoid violations. However, I don't always want to keep
that DEFAULT; going forward after the initial add, I want an error to occur
if there are inserts where this data is missing. So I have to DROP DEFAULT
On Thu, Aug 1, 2013 at 7:10 PM, Richard Broersma richard.broer...@gmail.com
wrote:
Notice :
http://www.postgresql.org/docs/9.3/static/sql-altertable.html
After you add a column to your table, you can latter *alter* this column
to add, change, or remove the default expression. There's no
On Thu, Aug 1, 2013 at 10:25 AM, Sandeep Gupta gupta.sand...@gmail.comwrote:
@Jeff : Thanks for pointing this out. Turns out that was the case.
@Tom: Thank you for the reference to random_page_cost parameters. It would
be very useful for us. Would go through the rest of the documentation as
On Thu, Aug 1, 2013 at 7:53 PM, Adrian Klaver adrian.kla...@gmail.comwrote:
It fails because
ALTER TABLE x
ADD COLUMN data2 VARCHAR(10) NOT NULL DEFAULT 'foo',
end in , instead of ;
You have to add the column before you can alter it.
=/ That's the way I have it in the SQL Fiddle sample
I don't believe you can use JOIN explicitly in this situation because it's
an UPDATE, but I believe you can accomplish the same effect with FROM and
WHERE.
UPDATE table SET column1 = TRUE
FROM table2
WHERE table1.event_id = table2.event_id;
I would make sure there's an index on table2.event_id
I posted this question on StackOverflow, and the only person to answer
recommended I ask these lists for more details and link to the question:
http://stackoverflow.com/questions/16927331/postgresql-point-ops-with-gist-postgis-spatial-index
My question is:
The 9.0 release
.
** **
*From:* postgis-users-boun...@lists.osgeo.org [mailto:
postgis-users-boun...@lists.osgeo.org] *On Behalf Of *BladeOfLight16
*Sent:* Wednesday, June 05, 2013 2:29 PM
*To:* PostGIS Users Discussion; pgsql-general@postgresql.org
*Subject:* [postgis-users] point_ops with GiST PostGIS Spatial
37 matches
Mail list logo
