[SQL] copy from csv, variable filename within a function

[basti]

Hello,
i have try the following:

-- Function: wetter.copy_ignore_duplicate(character varying)
 
-- DROP FUNCTION wetter.copy_ignore_duplicate(character varying);
 
CREATE OR REPLACE FUNCTION wetter.copy_ignore_duplicate(_filename
character varying)
  RETURNS void AS
$BODY$
declare sql text;
 
BEGIN
CREATE TEMP TABLE tmp_raw_data
(
  "timestamp" timestamp without time zone NOT NULL,
  temp_in double precision NOT NULL,
  pressure double precision NOT NULL,
  temp_out double precision NOT NULL,
  humidity double precision NOT NULL,
  wdir integer NOT NULL,
  wspeed double precision NOT NULL,
  CONSTRAINT tmp_raw_data_pkey PRIMARY KEY ("timestamp")
)
ON COMMIT DROP;
 
 
--copy tmp_raw_data(
--   "timestamp", temp_in, pressure, temp_out, humidity, wdir,
wspeed)
 
--FROM '/home/wetter/csv/data/raw/2013/2013-04/2013-04-16.txt'
--WITH DELIMITER ',';
 
sql := 'COPY  tmp_raw_data(
--"timestamp", temp_in, pressure, temp_out, humidity, wdir,
wspeed) FROM ' || quote_literal(_filename) || 'WITH DELEMITER ',' ';
execute sql;
 
-- prevent any other updates while we are merging input (omit this if
you don't need it)
LOCK wetter.raw_data IN SHARE ROW EXCLUSIVE MODE;
-- insert into raw_data table
INSERT INTO wetter.raw_data(
"timestamp", temp_in, pressure, temp_out, humidity, wdir,
wspeed)
   
   SELECT "timestamp", temp_in, pressure, temp_out, humidity, wdir, wspeed
   FROM tmp_raw_data
   WHERE NOT EXISTS (SELECT 1 FROM wetter.raw_data
 WHERE raw_data.timestamp = tmp_raw_data.timestamp);
END;
$BODY$
  LANGUAGE plpgsql VOLATILE
  COST 100;
ALTER FUNCTION wetter.copy_ignore_duplicate(character varying)
  OWNER TO postgres;



But when i execute it i get the this error:
(sorry i don't know how to switch the error messages to English lang)
I think this a problem with escaping the delimiter


SELECT wetter.copy_ignore_duplicate(
'/home/wetter/csv/data/raw/2013/2013-04/2013-04-16.txt'
);
#
#
 
 
HINWEIS:  CREATE TABLE / PRIMARY KEY erstellt implizit einen Index
»tmp_raw_data_pkey« für Tabelle »tmp_raw_data«
CONTEXT:  SQL-Anweisung »CREATE TEMP TABLE tmp_raw_data ( "timestamp"
timestamp without time zone NOT NULL, temp_in double precision NOT NULL,
pressure double precision NOT NULL, temp_out double precision NOT NULL,
humidity double precision NOT NULL, wdir integer NOT NULL, wspeed double
precision NOT NULL, CONSTRAINT tmp_raw_data_pkey PRIMARY KEY
("timestamp") ) ON COMMIT DROP«
PL/pgSQL function "copy_ignore_duplicate" line 4 at SQL-Anweisung
FEHLER:  Anfrage »SELECT  'COPY  tmp_raw_data(
--"timestamp", temp_in, pressure, temp_out, humidity, wdir,
wspeed) FROM ' || quote_literal( $1 ) || 'WITH DELEMITER ',' '« hat 2
Spalten zurückgegeben
CONTEXT:  PL/pgSQL-Funktion »copy_ignore_duplicate« Zeile 29 bei Zuweisung
 
** Fehler **
 
FEHLER: Anfrage »SELECT  'COPY  tmp_raw_data(
--"timestamp", temp_in, pressure, temp_out, humidity, wdir,
wspeed) FROM ' || quote_literal( $1 ) || 'WITH DELEMITER ',' '« hat 2
Spalten zurückgegeben
SQL Status:42601
Kontext:PL/pgSQL-Funktion »copy_ignore_duplicate« Zeile 29 bei Zuweisung



-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql

Fwd: [SQL] copy from csv, variable filename within a function

[basti]

I have fixed it with dollar-quoting.

 Original-Nachricht 
Betreff:[SQL] copy from csv, variable filename within a function
Datum:  Thu, 18 Apr 2013 09:26:09 +0200
Von:basti 
An: pgsql-sql@postgresql.org



Hello,
i have try the following:

-- Function: wetter.copy_ignore_duplicate(character varying)
 
-- DROP FUNCTION wetter.copy_ignore_duplicate(character varying);
 
CREATE OR REPLACE FUNCTION wetter.copy_ignore_duplicate(_filename
character varying)
  RETURNS void AS
$BODY$
declare sql text;
 
BEGIN
CREATE TEMP TABLE tmp_raw_data
(
  "timestamp" timestamp without time zone NOT NULL,
  temp_in double precision NOT NULL,
  pressure double precision NOT NULL,
  temp_out double precision NOT NULL,
  humidity double precision NOT NULL,
  wdir integer NOT NULL,
  wspeed double precision NOT NULL,
  CONSTRAINT tmp_raw_data_pkey PRIMARY KEY ("timestamp")
)
ON COMMIT DROP;
 
 
--copy tmp_raw_data(
--   "timestamp", temp_in, pressure, temp_out, humidity, wdir,
wspeed)
 
--FROM '/home/wetter/csv/data/raw/2013/2013-04/2013-04-16.txt'
--WITH DELIMITER ',';
 
sql := 'COPY  tmp_raw_data(
--"timestamp", temp_in, pressure, temp_out, humidity, wdir,
wspeed) FROM ' || quote_literal(_filename) || 'WITH DELEMITER ',' ';
execute sql;
 
-- prevent any other updates while we are merging input (omit this if
you don't need it)
LOCK wetter.raw_data IN SHARE ROW EXCLUSIVE MODE;
-- insert into raw_data table
INSERT INTO wetter.raw_data(
"timestamp", temp_in, pressure, temp_out, humidity, wdir,
wspeed)
   
   SELECT "timestamp", temp_in, pressure, temp_out, humidity, wdir, wspeed
   FROM tmp_raw_data
   WHERE NOT EXISTS (SELECT 1 FROM wetter.raw_data
 WHERE raw_data.timestamp = tmp_raw_data.timestamp);
END;
$BODY$
  LANGUAGE plpgsql VOLATILE
  COST 100;
ALTER FUNCTION wetter.copy_ignore_duplicate(character varying)
  OWNER TO postgres;



But when i execute it i get the this error:
(sorry i don't know how to switch the error messages to English lang)
I think this a problem with escaping the delimiter


SELECT wetter.copy_ignore_duplicate(
'/home/wetter/csv/data/raw/2013/2013-04/2013-04-16.txt'
);
#
#
 
 
HINWEIS:  CREATE TABLE / PRIMARY KEY erstellt implizit einen Index
»tmp_raw_data_pkey« für Tabelle »tmp_raw_data«
CONTEXT:  SQL-Anweisung »CREATE TEMP TABLE tmp_raw_data ( "timestamp"
timestamp without time zone NOT NULL, temp_in double precision NOT NULL,
pressure double precision NOT NULL, temp_out double precision NOT NULL,
humidity double precision NOT NULL, wdir integer NOT NULL, wspeed double
precision NOT NULL, CONSTRAINT tmp_raw_data_pkey PRIMARY KEY
("timestamp") ) ON COMMIT DROP«
PL/pgSQL function "copy_ignore_duplicate" line 4 at SQL-Anweisung
FEHLER:  Anfrage »SELECT  'COPY  tmp_raw_data(
--"timestamp", temp_in, pressure, temp_out, humidity, wdir,
wspeed) FROM ' || quote_literal( $1 ) || 'WITH DELEMITER ',' '« hat 2
Spalten zurückgegeben
CONTEXT:  PL/pgSQL-Funktion »copy_ignore_duplicate« Zeile 29 bei Zuweisung
 
** Fehler **
 
FEHLER: Anfrage »SELECT  'COPY  tmp_raw_data(
--"timestamp", temp_in, pressure, temp_out, humidity, wdir,
wspeed) FROM ' || quote_literal( $1 ) || 'WITH DELEMITER ',' '« hat 2
Spalten zurückgegeben
SQL Status:42601
Kontext:PL/pgSQL-Funktion »copy_ignore_duplicate« Zeile 29 bei Zuweisung



-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql

[SQL] ALTER USER abc PASSWORD - what's going on ???

[Marcin Krawczyk]

Hi,

I can't change the pass for my user. When I invoke ALTER USER abc PASSWORD
newpassword
it changes ok but then I can't login with my newpassword...

It says authetication failed.
My pg_hba.conf has md5 entry for the ip I connect from. It used to work ok,
but I accidentaly changed the password for the user abc from pgAdmin and
now I can't change it back to what it was.

What's going on ?

regards
mk

Re: [SQL] ALTER USER abc PASSWORD - what's going on ???

[SEKA Bruno-Emmanuel]

Which version of postgresql.?

Sent from my Samsung Galaxy Note.
On 18 Apr 2013 11:01, "Marcin Krawczyk"  wrote:

> Hi,
>
> I can't change the pass for my user. When I invoke ALTER USER abc PASSWORD
> newpassword
> it changes ok but then I can't login with my newpassword...
>
> It says authetication failed.
> My pg_hba.conf has md5 entry for the ip I connect from. It used to work
> ok, but I accidentaly changed the password for the user abc from pgAdmin
> and now I can't change it back to what it was.
>
> What's going on ?
>
> regards
> mk
>

Re: [SQL] ALTER USER abc PASSWORD - what's going on ???

[Marcin Krawczyk]

I figured it out... when changing role from pgAdmin, it has a default VALID
UNTIL 1970 set and after confirming changes it just made my abc user
account invalid... but upon connecting postgres complains about pass
authetication, maybe the message should be changed ?

It's 9.1 by the way.

pozdrowienia
mk


2013/4/18 Marcin Krawczyk 

> Hi,
>
> I can't change the pass for my user. When I invoke ALTER USER abc PASSWORD
> newpassword
> it changes ok but then I can't login with my newpassword...
>
> It says authetication failed.
> My pg_hba.conf has md5 entry for the ip I connect from. It used to work
> ok, but I accidentaly changed the password for the user abc from pgAdmin
> and now I can't change it back to what it was.
>
> What's going on ?
>
> regards
> mk
>

Re: [SQL] ALTER USER abc PASSWORD - what's going on ???

[SEKA Bruno-Emmanuel]

OK then..

Sent from my Samsung Galaxy Note.
On 18 Apr 2013 11:22, "Marcin Krawczyk"  wrote:

> I figured it out... when changing role from pgAdmin, it has a default
> VALID UNTIL 1970 set and after confirming changes it just made my abc user
> account invalid... but upon connecting postgres complains about pass
> authetication, maybe the message should be changed ?
>
> It's 9.1 by the way.
>
> pozdrowienia
> mk
>
>
> 2013/4/18 Marcin Krawczyk 
>
>> Hi,
>>
>> I can't change the pass for my user. When I invoke ALTER USER abc
>> PASSWORD newpassword
>> it changes ok but then I can't login with my newpassword...
>>
>> It says authetication failed.
>> My pg_hba.conf has md5 entry for the ip I connect from. It used to work
>> ok, but I accidentaly changed the password for the user abc from pgAdmin
>> and now I can't change it back to what it was.
>>
>> What's going on ?
>>
>> regards
>> mk
>>
>
>

Re: [SQL] Peer-review requested of soft-delete scheme

[Jasen Betts]

On 2013-04-16, Mark Stosberg  wrote:

> My challenge is that I want to make very hard or impossible to access
> the soft-deleted rows through SELECT statements. There are lots of
> selects statements in the system.
>
> My current idea is to rename the "foo" table to something that would
> stand-out like "foo_with_deleted_rows". Then we would create a view
> named "foo" that would select all the rows except the soft-deleted views.

[...]

> Is this sensible? Is there another approach to soft-deletes I should be
> considering?

yes, rename the table and replace it with a view that excludes the soft
deleted records. Make "do instead" rules to handle inserts, updates
and deletes on the view by rediecting them to the base table.

-- 
⚂⚃ 100% natural



-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql

Re: [SQL] copy from csv, variable filename within a function

[bricklen]

Note: "DELEMITER" should be "DELIMITER".


On Thu, Apr 18, 2013 at 1:34 AM, basti  wrote:

>  I have fixed it with dollar-quoting.
>
>  Original-Nachricht   Betreff: [SQL] copy from csv,
> variable filename within a function  Datum: Thu, 18 Apr 2013 09:26:09
> +0200  Von: bastiAn:
> pgsql-sql@postgresql.org
>
>
>  Hello,
> i have try the following:
>
> -- Function: wetter.copy_ignore_duplicate(character varying)
>
> -- DROP FUNCTION wetter.copy_ignore_duplicate(character varying);
>
> CREATE OR REPLACE FUNCTION wetter.copy_ignore_duplicate(_filename
> character varying)
>   RETURNS void AS
> $BODY$
> declare sql text;
>
> BEGIN
> CREATE TEMP TABLE tmp_raw_data
> (
>   "timestamp" timestamp without time zone NOT NULL,
>   temp_in double precision NOT NULL,
>   pressure double precision NOT NULL,
>   temp_out double precision NOT NULL,
>   humidity double precision NOT NULL,
>   wdir integer NOT NULL,
>   wspeed double precision NOT NULL,
>   CONSTRAINT tmp_raw_data_pkey PRIMARY KEY ("timestamp")
> )
> ON COMMIT DROP;
>
>
> --copy tmp_raw_data(
> --   "timestamp", temp_in, pressure, temp_out, humidity, wdir,
> wspeed)
>
> --FROM '/home/wetter/csv/data/raw/2013/2013-04/2013-04-16.txt'
> --WITH DELIMITER ',';
>
> sql := 'COPY  tmp_raw_data(
> --"timestamp", temp_in, pressure, temp_out, humidity, wdir,
> wspeed) FROM ' || quote_literal(_filename) || 'WITH DELEMITER ',' ';
> execute sql;
>
> -- prevent any other updates while we are merging input (omit this if
> you don't need it)
> LOCK wetter.raw_data IN SHARE ROW EXCLUSIVE MODE;
> -- insert into raw_data table
> INSERT INTO wetter.raw_data(
> "timestamp", temp_in, pressure, temp_out, humidity, wdir,
> wspeed)
>
>SELECT "timestamp", temp_in, pressure, temp_out, humidity, wdir, wspeed
>FROM tmp_raw_data
>WHERE NOT EXISTS (SELECT 1 FROM wetter.raw_data
>  WHERE raw_data.timestamp = tmp_raw_data.timestamp);
> END;
> $BODY$
>   LANGUAGE plpgsql VOLATILE
>   COST 100;
> ALTER FUNCTION wetter.copy_ignore_duplicate(character varying)
>   OWNER TO postgres;
>
>
>
> But when i execute it i get the this error:
> (sorry i don't know how to switch the error messages to English lang)
> I think this a problem with escaping the delimiter
>
>
> SELECT wetter.copy_ignore_duplicate(
> '/home/wetter/csv/data/raw/2013/2013-04/2013-04-16.txt'
> );
> #
> #
>
>
> HINWEIS:  CREATE TABLE / PRIMARY KEY erstellt implizit einen Index
> »tmp_raw_data_pkey« für Tabelle »tmp_raw_data«
> CONTEXT:  SQL-Anweisung »CREATE TEMP TABLE tmp_raw_data ( "timestamp"
> timestamp without time zone NOT NULL, temp_in double precision NOT NULL,
> pressure double precision NOT NULL, temp_out double precision NOT NULL,
> humidity double precision NOT NULL, wdir integer NOT NULL, wspeed double
> precision NOT NULL, CONSTRAINT tmp_raw_data_pkey PRIMARY KEY
> ("timestamp") ) ON COMMIT DROP«
> PL/pgSQL function "copy_ignore_duplicate" line 4 at SQL-Anweisung
> FEHLER:  Anfrage »SELECT  'COPY  tmp_raw_data(
> --"timestamp", temp_in, pressure, temp_out, humidity, wdir,
> wspeed) FROM ' || quote_literal( $1 ) || 'WITH DELEMITER ',' '« hat 2
> Spalten zurückgegeben
> CONTEXT:  PL/pgSQL-Funktion »copy_ignore_duplicate« Zeile 29 bei Zuweisung
>
> ** Fehler **
>
> FEHLER: Anfrage »SELECT  'COPY  tmp_raw_data(
> --"timestamp", temp_in, pressure, temp_out, humidity, wdir,
> wspeed) FROM ' || quote_literal( $1 ) || 'WITH DELEMITER ',' '« hat 2
> Spalten zurückgegeben
> SQL Status:42601
> Kontext:PL/pgSQL-Funktion »copy_ignore_duplicate« Zeile 29 bei Zuweisung
>
>
>
> --
> Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
> To make changes to your 
> subscription:http://www.postgresql.org/mailpref/pgsql-sql
>
>
>
>

[SQL] Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help

[Sofer, Yuval]

Hi,



I am using Postgres DB with stand by database, configured with streaming in 
synchronized mode (each commit on primary DB waits for commit on secondary DB).



Sometimes we suffer from network issues and as consequences, secondary machine 
is not available.



In these situations, our application is stuck and do not respond anymore, since 
no confirmation comes from the secondary Postgres (obviously... it is down or 
unavailable).



Is there any parameter that I can use, to enable recovering from hanging on 
until someone of us re-establish connection to secondary DB?

Maybe some configuration parameter that sets the time interval for being stuck 
because of unavailable secondary Postgres?



Please help,



Thanks,



Yuval Sofer
BMC Software
CTM&D Business Unit
DBA Team
972-52-4286-282
yuval_so...@bmc.com

Re: [SQL] Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help

[Andreas Kretschmer]

Sofer, Yuval  wrote:

> Hi,
> 
>  
> 
> I am using Postgres DB with stand by database, configured with streaming in
> synchronized mode (each commit on primary DB waits for commit on secondary 
> DB).
> 
>  
> 
> Sometimes we suffer from network issues and as consequences, secondary machine
> is not available.
> 
>  
> 
> In these situations, our application is stuck and do not respond anymore, 
> since
> no confirmation comes from the secondary Postgres (obviously… it is down or
> unavailable….).
> 
>  
> 
> Is there any parameter that I can use, to enable recovering from hanging on
> until someone of us re-establish connection to secondary DB?

Use asynchronous mode. There is no way for 'only a little bit
synchronized mode'. We are not in the mysql-world ...



Andreas
-- 
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect.  (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly."   (unknown)
Kaufbach, Saxony, Germany, Europe.  N 51.05082°, E 13.56889°


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql

Re: [SQL] ALTER USER abc PASSWORD - what's going on ???

[Guillaume Lelarge]

On Thu, 2013-04-18 at 13:21 +0200, Marcin Krawczyk wrote:
> I figured it out... when changing role from pgAdmin, it has a default VALID
> UNTIL 1970 set and after confirming changes it just made my abc user
> account invalid...

FYI, this pgAdmin bug has been fixed. The fix will be available in the
next minor release.


-- 
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com



-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql

[SQL] SQL query with Overlapping date time ranges

[chinnaobi]

I have a temporary table with columnszone_name, nodeid, nodelabel,
nodegainedservice, nodelostserviceZone1, 3, Windows-SRV1, "2012-11-27
13:10:30+08", "2012-11-27 13:00:40+08"Zone1, 5, Windows-SRV2,
"2012-12-20 13:10:30+08", "2012-12-18 13:00:40+08"Many zones
and many nodes and same nodes with gained service and lost service many
times.`nodegainedservice` meaning node has come alive and `nodelostservice`
meaning node has gone down.How could I make a query to fetch each zone
availability in a period?e.g., Zone1 have Windows-SRV1, Windows-SRV2. Find
how many times and how long both servers are down at the same time or Zone1
is down.Please use the below sample datazonename, nodeid, nodelabel,
noderegainedservice, nodelostserviceZone1   27  Srv12013-02-21 
10:04:56+08
2013-02-21 09:48:48+08Zone1 27  Srv12013-02-21 10:14:01+08  
2013-02-21
10:09:27+08Zone127  Srv12013-02-21 10:26:29+08  2013-02-21 
10:24:20+08Zone1
27  Srv12013-02-21 11:27:24+08  2013-02-21 11:25:15+08Zone1 27  
Srv1
2013-02-28 16:24:59+08  2013-02-28 15:52:59+08Zone1 27  Srv1
2013-02-28
16:56:19+08 2013-02-28 16:40:18+08Zone1 27  Srv12013-02-28 
17:09:28+08
2013-02-28 16:58:38+08Zone1 27  Srv12013-02-28 17:39:50+08  
2013-02-28
17:29:47+08Zone127  Srv12013-03-01 09:39:36+08  2013-02-28 
19:12:26+08Zone1
27  Srv12013-03-01 13:35:07+08  2013-03-01 12:10:03+08Zone1 27  
Srv1
2013-03-04 11:04:14+08  2013-03-04 10:48:07+08Zone1 27  Srv1
2013-03-06
16:36:56+08 2013-03-06 16:33:10+08Zone1 27  Srv12013-03-13 
13:54:11+08
2013-03-06 16:43:51+08Zone1 27  Srv12013-03-14 11:43:28+08  
2013-03-13
19:09:31+08Zone127  Srv12013-03-18 18:38:16+08  2013-03-15 
18:55:31+08Zone1
27  Srv12013-03-22 11:18:57+08  2013-03-22 09:53:38+08Zone1 27  
Srv1
2013-03-28 16:48:27+08  2013-03-26 10:23:47+08Zone1 27  Srv1
2013-04-04
10:33:24+08 2013-04-04 10:32:51+08Zone1 27  Srv12013-04-04 
11:48:54+08
2013-04-04 11:48:23+08Zone1 27  Srv12013-04-08 19:01:34+08  
2013-04-08
19:01:03+08Zone127  Srv12013-04-08 19:37:05+08  2013-04-08 
19:31:38+08Zone1
27  Srv12013-04-08 21:48:07+08  2013-04-08 21:47:35+08Zone1 27  
Srv1
2013-04-08 21:54:02+08  2013-04-08 21:52:29+08Zone1 27  Srv1
2013-04-10
09:33:53+08 2013-04-10 09:32:34+08Zone1 27  Srv12013-04-10 
12:01:01+08
2013-04-10 12:00:30+08Zone1 27  Srv12013-04-10 14:57:25+08  
2013-04-10
14:56:53+08Zone127  Srv12013-04-10 16:25:50+08  2013-04-10 
16:24:31+08Zone1
27  Srv12013-04-10 16:57:02+08  2013-04-10 16:56:19+08Zone1 27  
Srv1
2013-04-10 17:17:37+08  2013-04-10 17:15:18+08Zone1 27  Srv1
2013-04-11
21:35:43+08 2013-04-11 21:31:50+08Zone1 39  Srv22013-04-05 
13:15:53+08
2013-04-05 12:26:04+08Zone1 39  Srv22013-04-05 13:23:10+08  
2013-04-05
13:21:14+08Zone139  Srv22013-04-05 13:35:23+08  2013-04-05 
13:33:32+08Zone1
39  Srv22013-04-05 15:17:25+08  2013-04-05 14:25:51+08Zone1 39  
Srv2
2013-04-07 16:49:56+08  2013-04-05 17:43:01+08Zone1 39  Srv2
2013-04-09
22:32:19+08 2013-04-07 20:00:44+08Zone1 39  Srv22013-04-09 
22:38:02+08
2013-04-09 22:37:40+08Zone1 39  Srv22013-04-10 11:16:21+08  
2013-04-10
11:13:32+08Zone139  Srv22013-04-10 16:15:37+08  2013-04-10 
15:44:05+08Zone1
39  Srv22013-04-10 16:23:07+08  2013-04-10 16:20:59+08Zone1 39  
Srv2
2013-04-10 16:48:46+08  2013-04-10 16:33:29+08Zone1 39  Srv2
2013-04-10
17:19:11+08 2013-04-10 17:04:10+08Zone1 39  Srv22013-04-11 
21:39:21+08
2013-04-11 21:28:51+08Zone1 39  Srv22013-04-11 22:05:02+08  
2013-04-11
21:49:44+08Zone139  Srv22013-04-15 14:02:11+08  2013-04-12 
16:41:48+08Zone1
39  Srv22013-04-17 00:00:00+08  2013-04-15 20:50:40+08Zone1 29  
Srv3
2013-03-12 17:20:02+08  2013-03-12 17:16:49+08Zone1 29  Srv3
2013-03-12
18:08:30+08 2013-03-12 17:55:43+08Zone1 13  Srv42013-01-09 
17:23:59+08
2013-01-09 17:19:13+08Zone1 13  Srv42013-01-10 16:54:27+08  
2013-01-10
16:53:48+08Zone113  Srv42013-01-10 16:59:55+08  2013-01-10 
16:56:56+08Zone1
13  Srv42013-01-10 17:07:10+08  2013-01-10 17:04:11+08Zone1 13  
Srv4
2013-01-10 17:13:54+08  2013-01-10 17:10:42+08Zone1 13  Srv4
2013-01-16
10:31:45+08 2013-01-15 14:47:25+08Zone1 13  Srv42013-01-24 
17:52:35+08
2013-01-24 17:20:31+08Zone1 13  Srv42013-01-28 17:24:25+08  
2013-01-28
16:53:10+08Zone113  Srv42013-02-18 12:16:45+08  2013-02-18 
12:10:05+08Zone1
13  Srv42013-02-18 15:00:26+08  2013-02-18 14:12:04+08Zone1 13  
Srv4
20