you have:
GROUP BY users.gender, measures.option
instead try:
GROUP BY users
On Wed, Jul 2, 2014 at 12:55 PM, Arup Rakshit
wrote:
> Hi,
>
> I am working on web development project. There I am using this awesome DB.
> Let
> me tell you first the schema that I am having associated the problem.
>
On Wed, Jul 2, 2014 at 1:44 PM, Arup Rakshit
wrote:
>
> *group by* on full table(*users*). I am away from our production DB. Could
> you
> tell me how this little change will solve the whole problem and help me to
> get
> the data as per the format I am looking for.
>
Arup,
I meant:
GROUP BY use
My full function works fine as a standalone python script, but I was having
trouble getting it to work in Posgres.
Outside of Postgres it worked fine (because I was feeding in lists of dates
to test on).
The I did the script with psycopg2 calling in the below table and it worked
fine. (in the do
On Sun, Mar 23, 2014 at 12:11 PM, Adrian Klaver
wrote:
>
> Intended:
>
> http://www.postgresql.org/docs/9.3/interactive/plpython-data.html
>
> FYI, it would be a good idea to include the Postgres version. plpython has
> been undergoing a lot of changes recently, so it would help to peg where
> you
I know Centos 4 is EOL, but will there be a REL/Centos 4 release of
postgres 8.4.17? The latest here is 8.4.16:
http://yum.postgresql.org/8.4/redhat/rhel-4-i386/repoview/
If not, thanks for the many Centos 4 packages over the years.
--
Jared Beck - Singlebrook - (607) 330-1493
--
Sent via
Thanks Devrim and Martin. I'm pushing hard for an OS upgrade.
On Sun, Apr 7, 2013 at 4:22 PM, Devrim GÜNDÜZ wrote:
>
> Hi,
>
> On Sat, 2013-04-06 at 17:16 -0400, Jared Beck wrote:
>> I know Centos 4 is EOL, but will there be a REL/Centos 4 release of
>> postgre
ique
constraint "visitor_referal_code_unique_btree_idx"
So now I am back to wondering if this problem originated when I think that it
did
(between 2005/02/22 00:00:00 and 2005/02/22 01:00:00) or if this could have been
hiding under the surface for longer than that.
I am suspecting a hardware
Is there a way for me to quickly calculate the maximum size of a row
for a table? I wanted to know if there was an automatic way to do it
before I do it manually.
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an app
.85
There's still a difference between the two reported tuple size of
atablename: 2047.95 - 1660.85 = 387.10
Can someone shed some more light on this and which one more closely
approximates the size of the tuples?
Jared
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
just happen? Or did someone here have to accidentally do something
to create it.
Sorry for not having any idea on what caused this, but thanks for any help you can
give.
Jared
---(end of broadcast)---
TIP 2: you can get off all lists at once
Tom Lane wrote:
Jared Carr <[EMAIL PROTECTED]> writes:
Item 2 -- Length: 148 Offset: 6860 (0x1acc) Flags: USED
XID: min (46034931) CMIN|XMAX: 2 CMAX|XVAC: 0
Block Id: 27 linp Index: 2 Attributes: 23 Size: 28
infomask: 0x2910 (HASOID|XMIN_COMMITTED|XMAX_INVALID|U
ve checked the newsgroups/blogs/websites and there doesn't seem to
be any major problems with using 7.4 version. If you are a DBA/system
admin at your company and currently using 7.4 for critical data
storing, please post your experiences and if they were positive or
negative.
Just looking for understanding/ideas.
I assume when people use dashboards they are not being queried every
second for updating but maybe every minute?
Are there any tools that work good on top of postgres?
(I see in the stock market (though I am looking at/for production data)
they seem to
add_one(num1) which gave a different
error.
Is this even possible? To have a "trigger" based on a select statement. I
looked at the SQL
TRIGGER command and it seems to only work for INSERT, UPDATE and DELETE. I
need a "trigger"
for SELECT's.
Thanks,
Jared H.
14 matches
Mail list logo
