If traffic has 5 records on a date and sales has 4 on the same date you would
output 20 records for that date.
Instead of dealing with the entire table just pick out a couple of dates and
show the results of the join in detail instead of just counts.
David J.
On Jul 11, 2011, at 22:53, Tim Uc
I have three tables. traffic, sales and dates. Both the traffic table
and the sales table has multiple entries per date with each row
representing the date, some subdivision, and the total. For example
every day five divisions could be reporting their sales so there would
be five entries in the sa
On Tue, 2011-07-12 at 01:12 +0100, Matthew Byrne wrote:
> I have a large database full of irreplaceable data, and due to a
> ridiculous happenstance I accidentally executed this code (as a superuser,
> of course):
>
> DELETE FROM pg_catalog.pg_type;
>
> Now the database is *seriously* unhappy - e
I am using query_to_xml with nulls set to false in postgresql 9.0.4. (I
believe the behavior was also present in 8.4.)
The documentation for query_to_xml says that if set to true, nulls with
be treated with xsi:nil="true" and "An appropriate namespace declaration
will be added to the result value
On Mon, Jul 11, 2011 at 6:25 PM, Craig Ringer
wrote:
> On 12/07/11 08:12, Matthew Byrne wrote:
>> I have a large database full of irreplaceable data, and due to a
>> ridiculous happenstance I accidentally executed this code (as a superuser,
>> of course):
>>
>> DELETE FROM pg_catalog.pg_type;
>>
>
On Mon, Jul 11, 2011 at 12:49 PM, David Johnston wrote:
> I do not see how recursive queries (really iteration of records) even enters
> the picture...
I agree, FWIW. If the feature was that desirable, we could look at
questions of implementation to make recursion either unnecessary or at
least
On 12/07/11 08:12, Matthew Byrne wrote:
> I have a large database full of irreplaceable data, and due to a
> ridiculous happenstance I accidentally executed this code (as a superuser,
> of course):
>
> DELETE FROM pg_catalog.pg_type;
>
> Now the database is *seriously* unhappy - every SQL command
On 12/07/11 08:12, Matthew Byrne wrote:
> I have a large database full of irreplaceable data, and due to a
> ridiculous happenstance I accidentally executed this code (as a superuser,
> of course):
>
> DELETE FROM pg_catalog.pg_type;
>
> Now the database is *seriously* unhappy - every SQL command
On Mon, Jul 11, 2011 at 12:50 PM, Gauthier, Dave
wrote:
> http://gigaom.com/cloud/facebook-trapped-in-mysql-fate-worse-than-death/
>
>
>
> How would PG stack up in a usage situation like this?
My sense is that Pg would stack up no better. I suspect to make this
work at this scale you'd have to
Hello,
I’m having a problem with concurrent processing.
2 queries are accessing the same parent table that have 24 partitions.
I see “shared lock is not granted “ for one of them on one of the children
while the other query is running.
Does the “ select from a parent table” make a lock on the
I have a large database full of irreplaceable data, and due to a
ridiculous happenstance I accidentally executed this code (as a superuser,
of course):
DELETE FROM pg_catalog.pg_type;
Now the database is *seriously* unhappy - every SQL command returns an
error message. How do I get at my data?
Hi,
Is there any way to effect behavior similar to the following:
FOREIGN KEY (field1, field2)
REFERENCES table2 (field1, field2)
ON UPDATE CASCADE
ON DELETE (SET field2 = NULL) -- leaving field1 with whatever value is
currently holds
With MATCH SIMPLE the NULL in field2 is sufficien
On Mon, Jul 11, 2011 at 03:53:20PM -0500, Merlin Moncure wrote:
> example, it's not clear why 1,800 servers running mysql is necessarily
> a 'fate worse than death'.
Speaking personally, I find even one server running mysql (if it's my
responsibility) is pretty enervating. I can imagine 1,800 co
On Mon, Jul 11, 2011 at 2:50 PM, Gauthier, Dave wrote:
> http://gigaom.com/cloud/facebook-trapped-in-mysql-fate-worse-than-death/
Well, Stonebraker is pitching (for the Nth time) a "revolutionary"
platform, VoltDB, which naturally brings up concerns about bias. For
example, it's not clear why 1,8
Dne 11.7.2011 21:50, Gauthier, Dave napsal(a):
> http://gigaom.com/cloud/facebook-trapped-in-mysql-fate-worse-than-death/
>
> How would PG stack up in a usage situation like this?
This article (and the slashdot discussion) was already mentioned in the
pg-advocacy list
http://archives.postgresq
I will put my support for David Johnston's proposal, in principle, though minor
details of syntax could be changed if using "!" conflicts with something. --
Darren Duncan
David Johnston wrote:
On Mon, Jul 11, 2011 at 10:12 AM, Florian Pflug wrote:
On Jul11, 2011, at 07:08 , Darren Duncan wro
On 11/07/2011 20:19, David Salisbury wrote:
Hope someone's out there for this one. Basically I'm creating a summary
table of many
underlying tables in one select statement ( though that may have to
change ). My problem
can be shown in this example..
select my_function( timeofmeasurement, longit
select my_function( timeofmeasurement, longitude ) as solarnoon,
extract(epoch from ( timeofmeasurement - solarnoon ) as solardiff
( case when solardiff < 3600 then 'Y' else 'N' end ) as
within_solar_hour from
my_table;
But I get an error along the lines of
ERROR: column "sol
http://gigaom.com/cloud/facebook-trapped-in-mysql-fate-worse-than-death/
How would PG stack up in a usage situation like this?
On Mon, Jul 11, 2011 at 10:12 AM, Florian Pflug wrote:
> On Jul11, 2011, at 07:08 , Darren Duncan wrote:
>> Christopher Browne wrote:
>>> Vis-a-vis the attempt to do nested naming, that is "ns1.ns2.table1",
>>> there's a pretty good reason NOT to support that, namely that this
>>> breaks relatio
Hope someone's out there for this one. Basically I'm creating a summary table
of many
underlying tables in one select statement ( though that may have to change ).
My problem
can be shown in this example..
select my_function( timeofmeasurement, longitude ) as solarnoon,
extract(epoch
On Wednesday 06 July 2011 14:27:53 BangarRaju Vadapalli wrote:
>We want to monitor the performance of PostGRE database. Could anyone
> please suggest any tools tried/working successfully...
Munin will graph some usefull postgres stats. It's easy enough to graph
another datapoint by creating a
On Sun, Jul 10, 2011 at 10:14 PM, Adarsh Sharma
wrote:
> Dear all,
>
> Today I need to create a schema for my application website that allows user
> comments too.
>
> I think we have to maintain hierarchical data and it is very common as all
> sites are supporting this feature.
>
> Can somebody su
I'm trying to debug a jboss/hibernate application that uses PostgreSQL
as a backend, for which PostgreSQL is reporting a lot of queries as
taking around 4398046 ms (~73 minutes) plus or minus 10 ms to
complete. I have two questions about this.
First, when I look at the logs, the long queries appea
Folks,
In the last couple of weeks I've been approached by two PHP projects who
could use help improving/maintainig their PostgreSQL support.
One is Mediawiki, which just needs help with maintenance, testing, and
improving certain features like full text search.
The second is Joomla, which is in
On Mon, Jul 11, 2011 at 10:12 AM, Florian Pflug wrote:
> On Jul11, 2011, at 07:08 , Darren Duncan wrote:
>> Christopher Browne wrote:
>>> Vis-a-vis the attempt to do nested naming, that is "ns1.ns2.table1",
>>> there's a pretty good reason NOT to support that, namely that this
>>> breaks relationa
On Jul11, 2011, at 07:08 , Darren Duncan wrote:
> Christopher Browne wrote:
>> Vis-a-vis the attempt to do nested naming, that is "ns1.ns2.table1",
>> there's a pretty good reason NOT to support that, namely that this
>> breaks relational handling of tables. PostgreSQL is a *relational*
>> databas
Christopher Browne wrote:
> Vis-a-vis the attempt to do nested naming, that is "ns1.ns2.table1",
> there's a pretty good reason NOT to support that, namely that this
> breaks relational handling of tables. PostgreSQL is a *relational*
> database system, hence it's preferable for structures to b
Dear all,
Today I need to create a schema for my application website that allows
user comments too.
I think we have to maintain hierarchical data and it is very common as
all sites are supporting this feature.
Can somebody suggest me some guidelines to follow and some links too.
Thanks
-
On Jul8, 2011, at 08:21 , Darren Duncan wrote:
> Also, the proper way to do temporary tables would be to put them in
> another database than the main one, where the whole other database
> has the property of being temporary.
FWIW, Microsoft SQL Server does it that way, and as a result temporary
ta
Christopher Browne wrote:
Vis-a-vis the attempt to do nested naming, that is "ns1.ns2.table1",
there's a pretty good reason NOT to support that, namely that this
breaks relational handling of tables. PostgreSQL is a *relational*
database system, hence it's preferable for structures to be
relatio
31 matches
Mail list logo
