On 19 October 2017 at 17:25, Scott Mead wrote:
>
>
> On Thu, Oct 19, 2017 at 11:21 AM, Igal @ Lucee.org wrote:
>>
>> Hello,
>>
>> In other database servers, which I'm finally dropping in favor of
>> Postgres, I can do the following (mind you that this is for illustration
>> only, I do not actuall
x27;m not that familiar with JSONB, but wouldn't it be possible to create an
index over an organisation-specific JSON 'blob' such that all fields in it are
part of the index? I expect that index types aimed at text searches (word
searches) would be useful in that r
JOINs, because you use columns
from the right-hand side (alloc_trans.tran_date and due_trans.tran_date
respectively) in your WHERE clauses without allowing them to be NULL. If you
want those parts to behave like proper LEFT JOINs, either add OR xxx.tran_date
IS NULL or move those expressions into t
On 20 September 2017 at 22:55, Job wrote:
> One further question: within a query launched on the MASTER table where i
> need to scan every table, for exaple to search rows locatd in more partitions.
> In there a way to improve "parallel scans" between more table at the same
> time or not?
> I no
On 20 September 2017 at 07:42, Job wrote:
> We use a "temporary" table, populated by pg_bulkload - it takes few minutes
> in this first step.
> Then, from the temporary table, datas are transferred by a trigger that copy
> the record into the production table.
> But *this step* takes really lots
rget record in the master table already exists. In our case,
we convert character fields to varchar (which saves a lot of space(s)).
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
Sent via pgsql-general mailing
On 8 September 2017 at 00:23, Jeff Janes wrote:
> On Tue, Aug 29, 2017 at 1:20 AM, Alban Hertroys wrote:
>>
>> On 28 August 2017 at 21:32, Jeff Janes wrote:
>> > On Mon, Aug 28, 2017 at 5:22 AM, Alban Hertroys
>> > wrote:
>> >>
>> >> H
On 15 September 2017 at 11:03, Rafal Pietrak wrote:
>> Isn't this typically handled with an inheritance (parent-children)
>> setup. MasterDocument has id, subtype and any common columns (create
>> date etc) then dependents use the same id from master to complete the
>> data for a given type. Th
On 28 August 2017 at 21:32, Jeff Janes wrote:
> On Mon, Aug 28, 2017 at 5:22 AM, Alban Hertroys wrote:
>>
>> Hi all,
>>
>> It's been a while since I actually got to use PG for anything serious,
>> but we're finally doing some experimentation @w
On 28 August 2017 at 14:22, Alban Hertroys wrote:
> This is on:
Just noticed I forgot to paste this in:
warehouse=# select version();
vers
Hi all,
It's been a while since I actually got to use PG for anything serious,
but we're finally doing some experimentation @work now to see if it is
suitable for our datawarehouse. So far it's been doing well, but there
is a particular type of query I run into that I expect we will
frequently use
ta + g.data, -- altered section, data is numeric(7,3)
>sg.depth + 1,
> path || g.id,
> g.id = ANY(path)
>FROM graph g, search_graph sg
>WHERE g.id = sg.link AND NOT cycle
> )
> SELECT * FROM search_graph;
I believe the solution is rather simpl
for example).
> I should state that like most database reads will be much more frequent than
> writes and inserts will be more frequent than updates (re-ordering)
More of the logic (and thus system load) gets moved to the read-side of things,
that's probably a drawback, but most of
plain once detected.
And I'm sure there are plenty of other corner-cases you need to take into
account. I bet it has a lot of problems in common with replication actually
(how do we reliably get information from system A to system B), so it probably
pays to look at what particular prob
e errors are?
My guess would be its user interface…
I would suggest gViM or MacViM, but that really depends on what you expect from
a (I)DE and on what platform you are.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
ut.append(String.format(" %3d", endTime - startTime));
> }
>
> stmt.close();
>
> System.out.println(out);
> }
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
Sent via pgsql-general
On 8 June 2017 at 17:27, greigwise wrote:
> So, I'm using postgres version 9.6.3 on a mac and the results to this series
> of queries seems very strange to me:
>
> db# select count(*) from table1 where id in
> (1706302,1772130,1745499,1704077);
> count
> ---
> 4
> (1 row)
>
> db# select
e is a better solution rather than creating two separated
> functions :(
You can use your boolean parameter inside the join condition:
[…] on (tfquery.a = main.a and ((type_f and tfquery.d = main.d) or not type_f))
Beware that you don't also have a column named type_f in that join somewher
> According to the documentation 'numeric_precision_radix' field should
> indicate what radix the value of 'numeric_precision' is stored.
>
> However, even though the radix is 2, the actual value is 32, which is
> not a radix 2.
https://en.wikipedia.org/w
), which incidentally moved several connections from the switch the
game-system was connected to to another switch. I never pinpointed it to UDP,
but then again, TCP would correct for the lost transfers (probably at the cost
of UDP traffic).
Perhaps you have a switch somewhere that's ove
xperience, people don't usually move around much, so you should
certainly be able to pinpoint them mostly to a specific area, right? (Hence my
suggestions for a country column or partitioning in squares)
> On 19 April 2017 at 22:50, Alban Hertroys wrote:
>>
>>> On 19 Apr 2017, a
dimensions, creating a matrix of partitions under a single master table. I
don't think PG has a simple way of doing that (yet) though; perhaps it's
possible by abusing multiple levels of inheritance, but that sounds like a bad
idea.
And of course, create your partitions sufficien
can't create any type of primary/unique index, like a
> composite F1,F2, F3, F4 index. (correct me if i am wrong please).
Correct, you'll most likely have to add a new one (unless someone comes up with
better suggestions).
Alban Hertroys
--
If you can't see the forest for the tr
On 7 April 2017 at 09:11, Günce Kaya wrote:
> Hi again,
>
> Sorry for delay.
>
> Guillaume, I read your answer for first question but It's not clear to me.
> The table has a column and index also use that column. so in that example, I
> think table size and index size should be equal. Why these ar
not
know who exactly those people are.
ISTR that there are some tools for this purpose, but the details escape me.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
Sent via pgsql-general mailing list (pgsql
nd on INSERT/UPDATE to be in sorted order. I'd
probably go with a BEFORE INSERT OR UPDATE trigger.
In addition, to prevent unsorted entry, on obj2 add CHECK (obj2 > obj1) and on
obj3 add CHECK (obj3 > obj2).
Now you can create a normal PK or unique key on (obj1, obj2, obj3) as the or
ES words_users(uid) CHECK (uid <> author) ON DELETE …
You put your CHECK constraint definition smack in the middle of the FK
constraint definition, which starts with REFERENCES and ends with the delete
CASCADE.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees
course did VACUUM ANALYZE and I have reset statistics But no sign. Is
> there any particular thing I should be looking at?
An EXPLAIN ANALYZE would be a good start.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
On 2 February 2017 at 14:57, Job wrote:
> Hi Raymond,
>
> Thank nyou for your appreciated feedback.
But what's your answer to his question? You still didn't tell.
> Here is the original message:
>
> i really strange problem, quite near to paranormal, is occurring during a
> server migration.
>
o is to remove them from your create statements. Most of
the time there is no benefit creating case-sensitive identifiers in a database.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
a. Unless you
have indexes on those fields in which they are cast to time AND the query
planner chooses to use those indexes, the type-cast will get applied to every
candidate record each. If you have a million candidate records, that's 2x a
million casts taking place (for two fields).
To say m
wdown" for a query
that goes from 1.5ms to 4ms?
What is the actual problem you're trying to solve? Because I don't see one in
the above.
Just saying, you're obviously worried about something, but should you be?
Alban Hertroys
--
If you can't see the forest for the trees,
cu
amp <@ '[2016-12-27 00:00:00, 2016-12-31 00:00:00)'::tsrange
The above isn't entirely correct, as tsrange uses timestamp without time zone,
but you get the gist.
However, if those time ranges can have other values than '[00:00. 23:59]', then
you probably need 2 indexe
close the connection, create a
new one or change the user's role, this procedure doesn't need calling again.
> Is this practical? Has anyone here done it? What might the caveats be?
It's a fairly common practice, the ML archives should contain plenty of
examples.
Alban Hertroys
f MVC. That's just something
that struck me to make more than a bit of sense…
Of course, for the actual view in the MVC paradigm there should be some kind of
user interface, but database views could be really useful in preparing the data
required for those, to make it fit the shape of the vi
Is it possible?
I have no idea what you're saying.
> On Wednesday, December 21, 2016, Alban Hertroys wrote:
>>
>> On 21 December 2016 at 09:59, Yogesh Sharma wrote:
>> > Also, every hour,i am performing VACUUM and REINDEX operation on table.
>>
>> Why
On 21 December 2016 at 09:59, Yogesh Sharma wrote:
> Also, every hour,i am performing VACUUM and REINDEX operation on table.
Why are you running REINDEX every hour? That's a very unusual thing to
do, you'd need a pretty good reason for that.
--
If you can't see the forest for the trees,
Cut the
re in, say TCL, should be able to
handle that. Or am I missing something?
Whether it's a good idea to let the database encode attachments and send
e-mails is a different matter, but if it isn't doing much beside that - well,
why not?
Alban Hertroys
--
If you can't see the forest
tainly possible.
>
> Francisco Olarte.
>
> Hi, I think you're right. I was surprised by the huge size of the tables in
> my tests but I had not considered the vacuum properly.
> My test had a really huge activity so perhaps the autovacuum didn't have time
> to make
On 16 November 2016 at 16:33, Rich Shepard wrote:
> On Tue, 15 Nov 2016, Rich Shepard wrote:
> If 9.6.1 is currently running after running initdb, and I can access my
> databases, what does pg_upgrade do that's necessary?
pg_upgrade migrates your databases from your old (9.5) cluster to the
ne
On 4 November 2016 at 11:20, Gionatan Danti wrote:
> Unfortuntaly I am working with incredible constrains from customer side;
> even buying two SAS disks seems a problem. Moreover, as an external
> consultant, I have basically no decision/buying power :|
> What I can do (and I did) is to raise a v
On 4 November 2016 at 14:41, Merlin Moncure wrote:
> On Fri, Nov 4, 2016 at 8:08 AM, Kim Rose Carlsen wrote:
>> The nulls are generated by something like this
>> SELECT c.circuit_id,
>>cc.customer_id
>>FROM circuit AS c
>> LEFT JOIN circuit_customer AS cc
>>
On 31 October 2016 at 15:50, Christofer C. Bell wrote:
>
> I think the OP's point is that having a hodgepodge of (on their face)
> unrelated commands smells kinda unorganized at best and unprofessional at
> worst. Wether or not he's right is up to the reader. For me, I agree with
> his sentimen
On 31 October 2016 at 14:41, Adrian Klaver wrote:
> On 10/31/2016 02:06 AM, Kiran wrote:
>> I know 94 = 1 + (3 * 31).
>> I am just having a normal insert statement into cf_question table.
>
> Are there any other triggers on the tables?
I'm fairly confident that the duplicates are from updates on
the
commit hook of your VC of choice.
Regards,
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
mns into account and delete
rows that belong to the OLD link and not to the NEW one (or do nothing if those
stayed the same)
- or you do nothing (no trigger needed) because in the majority of cases
changing FK's is limited to a few power users at best and they're supposed to
know what
On 28 October 2016 at 13:03, Alexander Farber
wrote:
> Hello,
>
> is it please possible to rewrite the SQL query
>
> SELECT DISTINCT ON (uid)
> uid,
> female,
> given,
> photo,
> place
> FROM words_social
> WHERE uid I
ert into person (fname, lname) values ('next', 'other');
>
> How would I issue an update statement to update the number column?
That depends on which order you want the database to perceive those rows in.
The above example suggests that alphabetical order on fname might wor
t? Did you contact
them about this behaviour yet? Might just be that they're familiar with the
problem and have a solution for it.
I suspect the Python script you're running was implemented as a rather rough
workaround by people from allianzgrp who knew just enough to be harmful. (Kill
-9
> On 10 Oct 2016, at 21:28, Alban Hertroys wrote:
>
>
>> On 10 Oct 2016, at 21:12, Periko Support wrote:
>>
>>for pid in idle_record:
>>try:
>> #print "process details",pid
>> #os.system("ki
e best way to go about this, and best of all, you can combine
that with your select statement.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
oad.eclipse.org/jetty/9.3.11.v20160721/apidocs/org/eclipse/jetty/util/ajax/JSON.html#parse-java.lang.String-
>
> fails with:
>
> java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast to
> java.util.List
I'm not 100% sure it's the root of the ClassCastException h
s? Shouldn't the result be:
{NULL,NULL,NULL}?
(Sorry for sort-of hijacking this thread)
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make ch
le PG servers in separate directories, running on
separate port numbers, you would have multiple clusters. Same if you distribute
those servers over several hosts, what you seem to think a cluster means. That
is the difference between a cluster of databases and a cluster of servers.
Alban Hertroy
hat looks something like this for sample size 4:
sample 1: (A + B + C + D)
sample 2: (A + B + C + D) + E - A = (B + C + D + E)
sample 3: (B + C + D + E) + F - B = (C + D + E + F)
etc.
To accomplish this, you calculate two cumulative totals (often misnamed as
running totals, but AFAIK that's so
As I understand it, sequences have to be non-transactional to be able to
guarantee correct ordering.
Calling nextval() will increment the sequence, but does not relate it to the
transaction at that point. The select statement that does the call to nextval()
receives the value from the sequence a
REATE OR REPLACE FUNCTION public.full_text_universal_cast(doc_data
>> "text")
>> RETURNS "tsvector" AS
>> $BODY$
>> SELECT to_tsvector('english', COALESCE(TRIM(CAST(doc_data AS TEXT)), ''));
>> $BODY$
>> LANGUAGE sql IMMUTABLE
d there. It
probably gets interpreted as a column name.
> END IF;
> IF (TG_OP = 'INSERT') THEN
> UPDATE public.companies SET client_code_increment =
> (client_code_increment + 1) WHERE id = NEW.id;
> END IF;
> RETURN NEW;
> END;
> $
On 4 May 2016 at 17:08, John McKown wrote:
> I had a manager, long ago, who used a Lotus 1-2-3 spreadsheet to
> contain all his memos. I was glassy eyed in disbelief. He also would use his
> hand calculator to add up the numbers in the spreadsheet to be sure that the
> summation function in the sp
dundancy in the
index would probably help:
create index gorfs.inodes_accounts_idx on gorfs.inodes (substring (full_path
from 20)) where full_path like '/userfiles/account/%';
and then use similar expressions in your query of course:
where full_path like '/userfiles/account/%&#
On 28 April 2016 at 08:36, Tim van der Linden wrote:
> On Wed, 27 Apr 2016 13:48:06 +0200
> Alban Hertroys wrote:
>
>> In this case, you're using the values in adverse to filter relevant rid's
>> for the FK join, so you might be better off with the inverse of abo
ck pain - nonspecific', 'nonspecific
back pain', 'back pain'])
AND d.drug = ANY (ARRAY[359, 360, 361, 362, 363])
) x ON x.rid = r.id
ORDER BY r.created;
Looking at the cardinality of your tables that does seem a bit unlikely though.
Still, worth a shot...
Alban
ly once, but
the slow-down is caused by having to do conversions (for two field values) for
every row.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.
timestamptz now() to a date ;)
That's basically what you're doing when you use current_date instead of now().
The reason that the other way around is so much more expensive is that
the database needs to do that conversion twice for every row in the
table. When down-converting now(),
s?
>
>
> We want create same mechanism.
>
> If the above questions did not already cover this, what mechanism?
>
>
> I know there are adv. locks in PG, but I want to use session id.
>
> This could be:
> |pg_backend_pid|()
>
> May pid repeats.
> Where
ore (or
can it restore using plain text sql scripts these days?) instead of psql.
Lastly, how does a database in unicode fare for text size (without toasted
values) against a plain text dump file in, say, utf-8 - which isn't even the
worst case scenario? That's the simplistic cas
o contain something a bit
more meaningful though...
Well, enough of my rambling!
Ad 1. It is possible that you cater for the possibility that you don't know
whether a "contact" has a phone number or not, in which case null would
probably be the wrong choice for "no phone
ough explain analyze again. It wouldn't
surprise me if that query is already significantly faster.
If you're still having problems at that point, post that query and the analysis
again.
> Explain analyze link:
> http://explain.depesz.com/s/5WJy
Alban Hertroys
--
If you can't
query-template with
enough placeholders and views that there is no way to predict how that's going
to perform without at least knowing what goes into the placeholders and how the
views are built up.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you&#
//github.com/stalkerg/postgres_cmake
>
> The compilation will be enough (tests even better). I need feedbacks so that
> create issues on github.
> Very interesting NetBSD, OpenBSD, Solaris.
I was under the impression that the FreeBSD port already uses cmake?
Alban Hertroys
--
If you can&#x
copying of columns" in your reply to Adrian's
solution, but I don't think that happens here.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
Sent via pgsql-general mailing list (pgsql-general@
d all Cocs at least 3 times in this whole
> conversation.
>
> Thanks,
> Regina
What about this for a CoC?:
1. Do not discuss a CoC.
But, this side-thread has been going on long enough I think. Let's wrap this
up, shall we?
Regards,
Alban Hertroys
--
If you can't
On 12 January 2016 at 09:25, Chris Travers wrote:
> One of the dangers of a CoC is that there are many potential issues which
> may or may not become real problems. I think if we try to be clear on all
> of them, then we risk creating codes instead of a general expectation of
> what we do expect
ople are all being so polite about it that it's almost
offensive!
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscriptio
to any standard
behaviour and could even behave differently or (more likely) not work at all on
other PG instances.
That said, it's not uncommon in BI to require a seq. scan anyway, in which case
the point is rather moot.
Regards,
Alban Hertroys
--
If you can't see the forest for th
to be
looking for is the list of possible unique combinations, as sets of elements of
the total set (sets are orderless).
with list_of_ids as (
select unnest(list_of_ids) as id from table
)
select a.id, b.id
from list_of_ids a, list_of_ids b
where b.id > a.id;
Alban Hertroys
--
If
e not all time zones are full
hours apart, or have the same (if any) DST change-over dates. For example,
India is currently at UTC+05:30, probably because they wrapped the entire
country in the same TZ after their independence.
Alban Hertroys
--
If you can't see the forest for the trees,
c
_stamp from dateRange;
I suspect generate_series is faster, but since your query already almost looked
like this I thought I'd offer this alternative approach. It has a little bit
more flexibility too, as you can add fields and calculations to the CTE quite
easily.
Alban Hertroys
a "pg_dump" to execute
Aren't you trying to move a database to PG 9.4? Then you need to use the
pg_dump and pg_restore utilities of the 9.4 installation, not those of the 9.3
one. Those utilities are guaranteed to be backwards compatible, but they're not
necessarily forwards
> Before I start in to implement a DELETE / AUTOVACUUM / VACUUM approach, to
> recycling disk space used for a session management table, I would like to
> propose, for consideration by this forum, an idea for a different approach.
>
> A row in a session management table, represents a significant "s
Please refrain from top-posting.
On 2 November 2015 at 10:48, Eelke Klein wrote:
> Normally we call this from within our windows program where a lot of code is
> involved for setting up the environment, and creating the pipes and
> redirecting stdout, stderr and stdin. However I believe it is the
et in the right mindset.
PS. I usually write my hierarchical queries in Oracle, which isn't quite as
good at them as Postgres is, but it's what we have @work. Hence, I'm not sure I
got the syntax 100% correct. We're working on getting PG in for a project
upgrade (replacing RDB
On 25 September 2015 at 13:08, Ramesh T wrote:
> CREATE UNIQUE INDEX idx_load_pick ON pick (case picked when picked='y' then
> load_id else null end );
>
> how can i convert case expressed to postgres..above it is oracle.
Assuming that your queries are written in such a way that Oracle is
indeed
On 11 August 2015 at 06:44, Mister Junk wrote:
> I'm using prepared statements to prevent SQL injection, but I have done some
> reading and it seems like using Prepared statements COULD improve
> performance. I understand the concept, but I do not know how to implement
> this.
They could, they c
OPY (SELECT * FROM viewname) TO "
>
>
> Still curious why the triggers I'm writing won't fire before my
> statement errors out on copying to a view, or inserting an out-of-range
> timestamp, when the trigger would resolve all the illegal operations if
> it jus
view in the COPY statement instead of the table.
Added bonus, you can now also use the view to export your table to the same CSV
format.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On 7 July 2015 at 12:55, Filipe Pina wrote:
> On Ter, Jul 7, 2015 at 1:41 , Adrian Klaver
> wrote:
>> Still not sure what is you are trying to accomplish. Is it really necessary
>> that every transaction be serialized? Or to put it another way, why are you
>> running in serializable by default? O
eed to with _named_ query
parameters, if those are available to you.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
^
It looks like you're trying to use 64-bit binaries on a 32-bit OS.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
On 21 May 2015 at 23:42, Karsten Hilbert wrote:
> You are right in the following aspect:
>
> - client sends in "NOW at HERE"
> - server knows HERE = UTC+2
And then the tectonic plate you're on shifts and you're suddenly in UTC+1 or +3
Thankfully, those things don't shift as fast as they sometim
On 22 May 2015 at 04:46, Bill Moran wrote:
> I did a litle research and it appears that neither Oracle nor db2 supports
> the 0xff syntax ... so not _quite_ as common as it seemed to me.
> With all that being said, if I were to build a patch, would it be likely
> to be accepted into core?
Wouldn
;
> The beauty of PostgreSQL is that you have both available and you
> can choose whichever is best for your situation.
>
> Agreed, though in my case I drop into plpythonu when I want more complex
> solutions.
>
>
>
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>
>
>
> --
> Melvin Davidson
> I reserve the right to fantasize. Whether or not you
> wish to share my fantasy is entirely up to you.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
to do some kind of query involving multiple customers.
That's easier to backup, sure, but you can't restore a single customer's schema
easily that way. So if one customer messes up their data big time, you'll need
to restore a backup for all customers in the DB.
Alban Hertro
On 2 April 2015 at 19:15, Taylor Brown wrote:
> So, I would rather put a check like this at the top of my function:
>
> --
> important_variable = (p_request::json->>'important_variable')::integer;
> IF (important_variable is NULL) THEN RAISE EXCEPTION 'important_variable
> must not be NULL.'; END
On 28 March 2015 at 02:14, Yuri Budilov wrote:
> I am new to PostgreSQL and Linux (coming across from Microsoft SQL Server).
>
> I installed PostgreSQL 9.4 on Oracle Linux 6.6 and its working ok (psql,
> etc).
> Now I try to install pgadmin3 on the same OS.
>
> I am having problems installing pda
No
>
>
>
> I need to do a count of comm failures by day, so I need to populate the
> check-in date field. Please help!
Easiest would be to insert the missing values in your table, something like:
WITH RECURSIVE calendar (missing_date) AS (
SELECT MAX(check_
On 19 March 2015 at 13:44, Raymond O'Donnell wrote:
> On 19/03/2015 12:39, jaime soler wrote:
>> El mié, 18-03-2015 a las 23:05 -0700, Rajagopal NS escribió:
>>> I have installed Postgres 9.0 in my machine. When I look at Programs and
>>> Features under Control Panel,
>>> I see the Size for Postgr
On 17 March 2015 at 15:30, Medhavi Mahansaria
wrote:
> Yes. I have read this document.
>
> But my issue is that even when it throws and exception I need to rollback
> the changes made by that query and move on to the next block.
>
> Is there any way to accomplish that?
Please do not toppost on th
On 16 March 2015 at 17:02, Rob Richardson wrote:
> Greetings!
>
>
>
> An update query is apparently succeeding, even though the query refers to
> fields that do not exist. Here’s the query:
>
>
>
> update inventory set
>
> x_coordinate = (select x_coordinate from bases where base = '101'),
>
> y_
t Relationship":
> > "SubPlan", "Subplan Name": "SubPlan 1", "Startup Cost": 0.00, "Total Cost":
> > 4.68, "Plan Rows": 1, "Plan Width": 8, "Plans": [ { "Node Type": "Seq Scan",
> &
1 - 100 of 1306 matches
Mail list logo
