Skip to content

Instantly share code, notes, and snippets.

@edgarcosta
Created April 9, 2019 22:08
Show Gist options
  • Save edgarcosta/2d8b459200ed96d248f47066f75239c6 to your computer and use it in GitHub Desktop.
Save edgarcosta/2d8b459200ed96d248f47066f75239c6 to your computer and use it in GitHub Desktop.
2019-04-07 16:13:59.700 EDT [18363] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-07 16:14:38.844 EDT [18564] editor@lmfdb LOG: duration: 12992.776 ms statement: SELECT "label", "coeffs", "degree", "r2", "cm", "iso_number", "disc_abs", "disc_sign", "disc_rad", "ramps", "galt", "class_number", "class_group", "used_grh", "rd" FROM "nf_fields" WHERE "degree" = 2 ORDER BY "degree", "disc_abs", "disc_sign", "iso_number"
2019-04-07 16:29:37.936 EDT [18564] editor@lmfdb LOG: duration: 2342.889 ms statement: SELECT "label", "coeffs", "degree", "r2", "cm", "iso_number", "disc_abs", "disc_sign", "disc_rad", "ramps", "galt", "class_number", "class_group", "used_grh", "rd" FROM "nf_fields" WHERE "degree" = 12 ORDER BY "degree", "disc_abs", "disc_sign", "iso_number"
2019-04-07 16:29:52.102 EDT [18564] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 01:38:58.730 EDT [16741] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 01:51:31.556 EDT [20154] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 01:52:56.018 EDT [21841] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 01:53:02.278 EDT [21853] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 02:30:06.231 EDT [40351] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 02:30:06.237 EDT [40345] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 02:30:10.023 EDT [34373] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
LEFT JOIN
(SELECT CASE WHEN waiting THEN 'waiting' WHEN state='idle' THEN 'idle' WHEN state LIKE 'idle in transaction%' THEN 'idletransaction' WHEN state='disabled' THEN 'unknown' WHEN query='<insufficient privilege>' THEN 'unknown' ELSE 'active' END AS mstate,
count(*) AS count
FROM pg_stat_activity WHERE pid != pg_backend_pid() AND datname='lmfdb'
GROUP BY CASE WHEN waiting THEN 'waiting' WHEN state='idle' THEN 'idle' WHEN state LIKE 'idle in transaction%' THEN 'idletransaction' WHEN state='disabled' THEN 'unknown' WHEN query='<insufficient privilege>' THEN 'unknown' ELSE 'active' END
) AS tmp2
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-08 02:35:10.105 EDT [36232] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 02:37:20.540 EDT [37560] roe@roe FATAL: password authentication failed for user "roe"
2019-04-08 02:37:20.540 EDT [37560] roe@roe DETAIL: Role "roe" does not exist.
Connection matched pg_hba.conf line 91: "local all all md5"
2019-04-08 02:37:20.540 EDT [37560] roe@roe LOG: could not send data to client: Broken pipe
2019-04-08 02:38:38.385 EDT [26816] webserver@lmfdb ERROR: permission denied for relation kwl_locks
2019-04-08 02:38:38.385 EDT [26816] webserver@lmfdb STATEMENT: SELECT username, timestamp FROM kwl_locks WHERE id = 'ec.mordell-weil' AND timestamp >= '2019-04-08T06:28:38.384614'::timestamp LIMIT 1
2019-04-08 02:38:38.385 EDT [26816] webserver@lmfdb ERROR: permission denied for relation kwl_locks
2019-04-08 02:38:38.385 EDT [26816] webserver@lmfdb STATEMENT: INSERT INTO kwl_locks (id, timestamp, username) VALUES ('ec.mordell-weil', '2019-04-08T06:38:38.385689'::timestamp, 'roed')
2019-04-08 12:50:05.487 EDT [26822] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 12:50:05.489 EDT [26828] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 12:50:05.491 EDT [26820] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 12:50:05.504 EDT [26823] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 12:50:05.506 EDT [26824] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 12:50:09.800 EDT [52319] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 12:55:09.117 EDT [54026] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 13:00:09.813 EDT [55684] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 13:05:09.594 EDT [57418] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 13:10:09.425 EDT [59116] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
count(*) AS count
FROM pg_stat_activity WHERE pid != pg_backend_pid() AND datname='lmfdb'
GROUP BY CASE WHEN waiting THEN 'waiting' WHEN state='idle' THEN 'idle' WHEN state LIKE 'idle in transaction%' THEN 'idletransaction' WHEN state='disabled' THEN 'unknown' WHEN query='<insufficient privilege>' THEN 'unknown' ELSE 'active' END
) AS tmp2
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-08 13:15:10.037 EDT [60879] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 13:20:09.259 EDT [62597] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
) AS tmp2
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-08 13:25:09.351 EDT [64333] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 13:30:09.143 EDT [814] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 13:35:09.100 EDT [2628] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 13:40:09.933 EDT [4345] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 13:45:09.843 EDT [6050] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 13:50:09.213 EDT [7807] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 13:55:10.043 EDT [9531] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 14:00:09.906 EDT [11231] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 14:05:09.417 EDT [13239] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 14:10:09.162 EDT [14980] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 14:15:09.956 EDT [16688] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 14:20:09.517 EDT [18414] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
FROM pg_stat_activity WHERE pid != pg_backend_pid() AND datname='lmfdb'
GROUP BY CASE WHEN waiting THEN 'waiting' WHEN state='idle' THEN 'idle' WHEN state LIKE 'idle in transaction%' THEN 'idletransaction' WHEN state='disabled' THEN 'unknown' WHEN query='<insufficient privilege>' THEN 'unknown' ELSE 'active' END
) AS tmp2
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-08 14:25:09.583 EDT [20221] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
GROUP BY CASE WHEN waiting THEN 'waiting' WHEN state='idle' THEN 'idle' WHEN state LIKE 'idle in transaction%' THEN 'idletransaction' WHEN state='disabled' THEN 'unknown' WHEN query='<insufficient privilege>' THEN 'unknown' ELSE 'active' END
) AS tmp2
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-08 14:30:10.556 EDT [22063] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-08 14:35:09.571 EDT [23966] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-08 14:40:09.364 EDT [25696] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 14:45:10.019 EDT [27489] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
ORDER BY 1;
2019-04-08 14:50:11.587 EDT [29209] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 14:55:09.789 EDT [30911] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
) AS tmp2
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-08 15:00:09.187 EDT [32650] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 15:05:09.280 EDT [34441] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 15:10:09.638 EDT [36207] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 15:15:10.071 EDT [37940] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 15:20:09.468 EDT [39621] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 15:25:10.179 EDT [41328] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 15:30:09.110 EDT [43037] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 15:35:09.975 EDT [44737] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
ORDER BY 1;
2019-04-08 15:40:09.730 EDT [46505] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 15:45:09.376 EDT [48213] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
FROM pg_stat_activity WHERE pid != pg_backend_pid() AND datname='lmfdb'
GROUP BY CASE WHEN waiting THEN 'waiting' WHEN state='idle' THEN 'idle' WHEN state LIKE 'idle in transaction%' THEN 'idletransaction' WHEN state='disabled' THEN 'unknown' WHEN query='<insufficient privilege>' THEN 'unknown' ELSE 'active' END
) AS tmp2
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-08 15:50:10.337 EDT [50036] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
FROM pg_stat_activity WHERE pid != pg_backend_pid() AND datname='lmfdb'
GROUP BY CASE WHEN waiting THEN 'waiting' WHEN state='idle' THEN 'idle' WHEN state LIKE 'idle in transaction%' THEN 'idletransaction' WHEN state='disabled' THEN 'unknown' WHEN query='<insufficient privilege>' THEN 'unknown' ELSE 'active' END
) AS tmp2
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-08 15:55:10.719 EDT [51752] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 16:00:09.458 EDT [53474] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 16:05:09.144 EDT [55208] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 16:10:10.058 EDT [56967] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 16:15:09.520 EDT [58655] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 16:20:09.948 EDT [60346] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 16:25:09.563 EDT [62062] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 16:30:09.141 EDT [63740] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 16:35:09.833 EDT [65444] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 16:40:09.051 EDT [2061] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 16:45:09.396 EDT [3774] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 16:50:09.950 EDT [5460] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 16:55:09.533 EDT [7213] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 17:00:09.024 EDT [8905] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 17:05:09.709 EDT [10629] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 17:10:09.468 EDT [12335] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 17:15:09.597 EDT [14040] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 17:20:09.235 EDT [15728] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 17:22:38.881 EDT [17432] editor@lmfdb LOG: duration: 2164.923 ms statement: SELECT "conrey_index", "embedding_index", "embedding_m", "embedding_root_real", "embedding_root_imag", "an_normalized"[2:10] FROM "mf_hecke_cc" WHERE "embedding_m" <= 20 AND "embedding_m" >= 1 AND "hecke_orbit_code" = 22519578718372771
2019-04-08 17:22:39.324 EDT [17679] editor@lmfdb LOG: duration: 1870.970 ms statement: SELECT "description", "degree", "label", "pretty", "real_dimension", "name" FROM "gps_sato_tate0" WHERE "name" = 'U(1)' LIMIT 1
2019-04-08 17:22:39.324 EDT [17606] editor@lmfdb LOG: duration: 1291.807 ms statement: SELECT "description", "degree", "label", "pretty", "real_dimension", "name" FROM "gps_sato_tate0" WHERE "name" = 'U(1)_2' LIMIT 1
2019-04-08 17:22:39.324 EDT [17715] editor@lmfdb LOG: duration: 1101.254 ms statement: SELECT "description", "degree", "label", "pretty", "real_dimension", "name" FROM "gps_sato_tate0" WHERE "name" = 'SU(2)xSU(2)' LIMIT 1
2019-04-08 17:22:39.324 EDT [17824] editor@lmfdb LOG: duration: 1766.044 ms statement: SELECT "description", "degree", "label", "pretty", "real_dimension", "name" FROM "gps_sato_tate0" WHERE "name" = 'USp(4)' LIMIT 1
2019-04-08 17:22:39.735 EDT [17550] editor@lmfdb LOG: duration: 9481.830 ms statement: SELECT "id" FROM "mf_hecke_cc" WHERE "hecke_orbit_code" = 274911461403 LIMIT 1
2019-04-08 17:22:40.641 EDT [17740] editor@lmfdb LOG: duration: 2215.545 ms statement: SELECT "ndim", "jacobian_decomp", "cc", "full_auto", "passport_label", "group", "signH", "label", "hyp_involution", "full_label", "eqn", "cinv", "hyperelliptic", "gen_vectors", "total_label", "g0", "dim", "group_order", "cyclic_trigonal", "r", "signature", "genus", "con", "braid", "topological", "realcc" FROM "hgcwa_passports" WHERE "passport_label" = '15.10-1.0.2-2-2-2-2-2-2-2-5.1' ORDER BY "genus", "dim", "cc"
2019-04-08 17:22:44.795 EDT [17592] editor@lmfdb LOG: duration: 1472.211 ms statement: SELECT "conrey_index", "embedding_index", "embedding_m", "embedding_root_real", "embedding_root_imag", "an_normalized"[2:10] FROM "mf_hecke_cc" WHERE "embedding_m" <= 20 AND "embedding_m" >= 1 AND "hecke_orbit_code" = 5291416489885
2019-04-08 17:22:44.880 EDT [17432] editor@lmfdb LOG: duration: 1533.223 ms statement: SELECT "conrey_index", "embedding_index", "embedding_m", "embedding_root_real", "embedding_root_imag", "an_normalized"[2:10] FROM "mf_hecke_cc" WHERE "embedding_m" <= 20 AND "embedding_m" >= 1 AND "hecke_orbit_code" = 412367192409
2019-04-08 17:22:45.702 EDT [17852] editor@lmfdb LOG: duration: 8503.928 ms statement: SELECT "orbit_label", "orbit_index", "parity", "is_real", "is_primitive", "galois_orbit", "conductor", "char_degree", "order", "modulus", "prim_orbit_index" FROM "char_dir_orbits" WHERE "modulus" <= 9999 AND "modulus" >= 25 AND "order" <= 7 AND "order" >= 5 AND "conductor" <= 49 AND "conductor" >= 25 ORDER BY "modulus", "orbit_index"
2019-04-08 17:22:47.935 EDT [17858] editor@lmfdb LOG: duration: 17420.220 ms statement: SELECT "orbit_label", "orbit_index", "parity", "is_real", "is_primitive", "galois_orbit", "conductor", "char_degree", "order", "modulus", "prim_orbit_index" FROM "char_dir_orbits" WHERE "modulus" <= 9999 AND "modulus" >= 3 AND "order" <= 3 AND "order" >= 3 AND "conductor" <= 9999 AND "conductor" >= 1 ORDER BY "modulus", "orbit_index"
2019-04-08 17:22:48.391 EDT [17806] editor@lmfdb LOG: duration: 18352.249 ms statement: SELECT "orbit_label", "orbit_index", "parity", "is_real", "is_primitive", "galois_orbit", "conductor", "char_degree", "order", "modulus", "prim_orbit_index" FROM "char_dir_orbits" WHERE "modulus" <= 9999 AND "modulus" >= 19 AND "order" <= 23 AND "order" >= 19 AND "conductor" <= 9999 AND "conductor" >= 1 ORDER BY "modulus", "orbit_index"
2019-04-08 17:22:51.881 EDT [17458] editor@lmfdb LOG: duration: 18094.787 ms statement: SELECT "label", "traces" FROM "mf_newspaces" WHERE "dim" >= 30000 AND "num_forms" IS NOT NULL ORDER BY "analytic_conductor", "level", "char_orbit_index"
2019-04-08 17:22:58.951 EDT [17448] editor@lmfdb LOG: duration: 23949.172 ms statement: SELECT "label", "dim", "hecke_orbit_code", "weight" FROM "mf_newforms" WHERE "traces"[37] = 0::numeric AND "traces"[3] = 0::numeric AND "weight" = 4 AND "level" = 244 ORDER BY "analytic_conductor", "level", "char_orbit_index", "hecke_orbit" LIMIT 1000
2019-04-08 17:24:20.728 EDT [17432] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.744 EDT [17458] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.761 EDT [17806] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.781 EDT [17448] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.787 EDT [17433] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.789 EDT [17858] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.794 EDT [17733] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.800 EDT [17521] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.811 EDT [17646] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.811 EDT [17852] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.818 EDT [17452] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.823 EDT [17443] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.833 EDT [17643] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.838 EDT [17556] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.840 EDT [17591] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.843 EDT [17656] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.844 EDT [17797] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.852 EDT [17534] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.856 EDT [17845] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.863 EDT [17565] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.866 EDT [17690] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.886 EDT [17592] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.893 EDT [17606] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.897 EDT [17824] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.902 EDT [17550] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.905 EDT [17783] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.905 EDT [17819] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.906 EDT [17679] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.915 EDT [17851] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.931 EDT [17642] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.937 EDT [17799] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.944 EDT [17715] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.950 EDT [17740] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.967 EDT [17677] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.971 EDT [17555] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:20.980 EDT [17854] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:21.002 EDT [17857] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:21.009 EDT [17478] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:21.058 EDT [17641] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:24:21.143 EDT [17816] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:34:06.522 EDT [22645] editor@lmfdb LOG: could not send data to client: Connection reset by peer
2019-04-08 17:34:06.522 EDT [22645] editor@lmfdb STATEMENT: SELECT "label", "coeffs", "degree", "r2", "cm", "iso_number", "disc_abs", "disc_sign", "disc_rad", "ramps", "galt", "class_number", "class_group", "used_grh", "rd" FROM "nf_fields" ORDER BY "degree", "disc_abs", "disc_sign", "iso_number"
2019-04-08 17:34:06.522 EDT [22645] editor@lmfdb FATAL: connection to client lost
2019-04-08 17:34:06.522 EDT [22645] editor@lmfdb STATEMENT: SELECT "label", "coeffs", "degree", "r2", "cm", "iso_number", "disc_abs", "disc_sign", "disc_rad", "ramps", "galt", "class_number", "class_group", "used_grh", "rd" FROM "nf_fields" ORDER BY "degree", "disc_abs", "disc_sign", "iso_number"
2019-04-08 17:34:59.196 EDT [22698] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 17:34:59.197 EDT [22698] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:04:56.194 EDT [33364] editor@lmfdb LOG: duration: 38665.019 ms statement: COMMIT
2019-04-08 18:22:57.722 EDT [41482] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.725 EDT [41692] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.733 EDT [41689] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.735 EDT [41484] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.743 EDT [41561] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.744 EDT [41550] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.747 EDT [41337] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.749 EDT [41698] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.754 EDT [41526] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.760 EDT [41722] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.762 EDT [41383] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.767 EDT [41696] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.769 EDT [41709] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.769 EDT [41597] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.770 EDT [41398] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.772 EDT [41694] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.777 EDT [41547] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.781 EDT [41611] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.783 EDT [41735] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.794 EDT [41711] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.795 EDT [41529] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.808 EDT [41664] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.845 EDT [41432] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.850 EDT [41741] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.861 EDT [41744] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:22:57.869 EDT [41487] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:28:33.064 EDT [35222] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:28:56.068 EDT [44382] editor@lmfdb LOG: duration: 2671.799 ms statement: COMMIT
2019-04-08 18:29:16.757 EDT [44173] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:16.776 EDT [44027] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:16.813 EDT [44051] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:16.814 EDT [44051] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:29:16.867 EDT [44283] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:16.867 EDT [44283] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:29:16.925 EDT [44009] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:16.932 EDT [44342] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:16.953 EDT [44144] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:16.959 EDT [44196] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:16.971 EDT [43999] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.003 EDT [44121] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.037 EDT [44004] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.042 EDT [44135] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.046 EDT [44224] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.062 EDT [44014] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.095 EDT [44071] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.096 EDT [44313] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.101 EDT [44055] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.135 EDT [44379] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.152 EDT [44090] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.156 EDT [44374] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.167 EDT [44162] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.192 EDT [44382] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.211 EDT [44373] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.211 EDT [44373] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:29:17.221 EDT [44164] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.252 EDT [44061] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.253 EDT [44105] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.261 EDT [44148] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.278 EDT [44336] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.278 EDT [44336] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:29:17.281 EDT [44181] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.282 EDT [44050] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.285 EDT [44408] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.286 EDT [44318] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.297 EDT [44409] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.307 EDT [44324] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.307 EDT [44324] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:29:17.326 EDT [44345] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.352 EDT [44171] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.377 EDT [44329] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.419 EDT [44385] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.450 EDT [44380] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:29:17.460 EDT [44381] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:47.722 EDT [47356] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:47.748 EDT [47458] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:47.749 EDT [47507] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:47.749 EDT [47507] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:32:47.784 EDT [47597] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:47.843 EDT [47462] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:47.889 EDT [47635] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.108 EDT [47777] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.112 EDT [47476] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.257 EDT [47383] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.281 EDT [47357] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.283 EDT [47559] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.284 EDT [47452] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.284 EDT [47452] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:32:48.285 EDT [47446] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.368 EDT [47697] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.385 EDT [47607] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.387 EDT [47450] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.387 EDT [47450] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:32:48.428 EDT [47605] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.430 EDT [47523] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.454 EDT [47478] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.457 EDT [47745] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.479 EDT [47761] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.479 EDT [47761] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:32:48.486 EDT [47691] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.535 EDT [47594] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.546 EDT [47388] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.589 EDT [47771] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.589 EDT [47771] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:32:48.699 EDT [47677] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.716 EDT [47619] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.726 EDT [47770] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.753 EDT [47758] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.768 EDT [47741] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.835 EDT [47714] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.886 EDT [47386] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.918 EDT [47644] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.975 EDT [47417] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:48.978 EDT [47711] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:49.016 EDT [47669] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:49.017 EDT [47669] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:32:49.020 EDT [47535] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:32:49.020 EDT [47535] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:32:49.027 EDT [47675] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:33:31.479 EDT [12641] editor@lmfdb LOG: duration: 9453.255 ms statement: UPDATE g2c_curves SET st_group = regexp_replace(st_group, '"(.*)"', '\1');
2019-04-08 18:46:04.885 EDT [54803] editor@lmfdb LOG: duration: 1045.773 ms statement: FETCH FORWARD 50 FROM "5"
2019-04-08 18:46:07.209 EDT [54445] editor@lmfdb LOG: duration: 2451.488 ms statement: FETCH FORWARD 100 FROM "9"
2019-04-08 18:46:07.574 EDT [54802] editor@lmfdb LOG: duration: 2388.499 ms statement: FETCH FORWARD 50 FROM "5"
2019-04-08 18:46:08.760 EDT [54412] editor@lmfdb LOG: duration: 1620.688 ms statement: FETCH FORWARD 2000 FROM "7"
2019-04-08 18:46:09.376 EDT [54445] editor@lmfdb LOG: duration: 2116.570 ms statement: COMMIT
2019-04-08 18:46:09.709 EDT [54802] editor@lmfdb LOG: duration: 2080.155 ms statement: COMMIT
2019-04-08 18:46:10.578 EDT [54411] editor@lmfdb LOG: duration: 8265.857 ms statement: FETCH FORWARD 50 FROM "1"
2019-04-08 18:46:10.973 EDT [54412] editor@lmfdb LOG: duration: 1637.853 ms statement: FETCH FORWARD 20 FROM "9"
2019-04-08 18:46:12.373 EDT [54445] editor@lmfdb LOG: duration: 2783.318 ms statement: FETCH FORWARD 100 FROM "11"
2019-04-08 18:46:12.568 EDT [54412] editor@lmfdb LOG: duration: 1537.556 ms statement: COMMIT
2019-04-08 18:47:11.340 EDT [54445] editor@lmfdb LOG: duration: 2623.594 ms statement: COMMIT
2019-04-08 18:47:32.117 EDT [54412] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.158 EDT [54445] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.167 EDT [54606] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.204 EDT [54411] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.257 EDT [54613] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.259 EDT [54805] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.455 EDT [54611] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.455 EDT [54611] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:47:32.474 EDT [54810] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.532 EDT [54418] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.588 EDT [54811] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.588 EDT [54639] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.589 EDT [54456] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.589 EDT [54456] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:47:32.609 EDT [54806] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.673 EDT [54571] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.685 EDT [54808] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.716 EDT [54618] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.732 EDT [54801] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.748 EDT [54623] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.766 EDT [54813] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.767 EDT [54569] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.767 EDT [54569] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:47:32.783 EDT [54619] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.847 EDT [54421] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.887 EDT [54812] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.908 EDT [54415] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.931 EDT [54573] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:32.931 EDT [54573] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:47:32.963 EDT [54463] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:33.020 EDT [54527] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:33.020 EDT [54527] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:47:33.038 EDT [54605] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:33.038 EDT [54605] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:47:33.042 EDT [54397] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:33.062 EDT [54803] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:33.103 EDT [54610] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:33.106 EDT [54555] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:33.143 EDT [54602] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:33.145 EDT [54807] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:33.217 EDT [54620] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:33.223 EDT [54506] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:33.264 EDT [54434] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:33.320 EDT [54802] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:33.359 EDT [54809] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:47:33.414 EDT [54804] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:48:29.530 EDT [12641] editor@lmfdb ERROR: relation "usrdb.dbrecord" does not exist at character 22
2019-04-08 18:48:29.530 EDT [12641] editor@lmfdb STATEMENT: SELECT COUNT(*) FROM usrdb.dbrecord;
2019-04-08 18:48:42.562 EDT [12641] editor@lmfdb LOG: duration: 8577.580 ms statement: SELECT COUNT(*) FROM userdb.dbrecord;
2019-04-08 18:49:11.799 EDT [12641] editor@lmfdb LOG: duration: 4907.856 ms statement: SELECT DISTINCT(username) FROM userdb.dbrecord;
2019-04-08 18:54:08.051 EDT [57939] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.075 EDT [58014] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.103 EDT [58071] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.103 EDT [58071] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:54:08.108 EDT [58309] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.123 EDT [58179] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.123 EDT [58253] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.150 EDT [58019] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.253 EDT [57931] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.258 EDT [58004] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.264 EDT [58052] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.277 EDT [58274] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.308 EDT [58000] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.322 EDT [58023] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.359 EDT [58260] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.366 EDT [58044] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.370 EDT [57935] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.382 EDT [58360] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.432 EDT [58256] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.454 EDT [58176] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.454 EDT [58176] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:54:08.479 EDT [58280] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.482 EDT [58079] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.491 EDT [58330] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.491 EDT [58330] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:54:08.494 EDT [58276] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.514 EDT [58261] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.537 EDT [57955] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.543 EDT [58341] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.561 EDT [58271] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.563 EDT [58192] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.565 EDT [58076] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.571 EDT [58322] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.588 EDT [58316] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.623 EDT [58102] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.638 EDT [58286] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.638 EDT [58286] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 18:54:08.665 EDT [58206] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.738 EDT [58074] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.780 EDT [58370] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 18:54:08.785 EDT [58236] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:01:07.001 EDT [61844] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:01:11.857 EDT [63006] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:01:41.762 EDT [61319] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:01:57.415 EDT [63088] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:02:08.195 EDT [63090] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:02:18.799 EDT [63094] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:02:27.803 EDT [63009] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:02:43.231 EDT [63095] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:03:47.749 EDT [63789] editor@lmfdb LOG: duration: 1023.214 ms statement: SELECT "label", "level", "weight", "dim", "analytic_conductor", "trace_display", "atkin_lehner_eigenvals", "qexp_display", "char_order", "hecke_orbit_code", "projective_image", "field_poly", "nf_label", "is_cm", "is_rm", "cm_discs", "rm_discs", "field_poly_root_of_unity", "field_poly_is_real_cyclotomic", "field_disc", "field_disc_factorization", "fricke_eigenval", "is_self_twist", "self_twist_discs" FROM "mf_newforms" WHERE "weight_parity" = 1 AND "char_parity" = 1 ORDER BY "analytic_conductor", "level", "char_orbit_index", "hecke_orbit" LIMIT 1000
2019-04-08 19:03:50.366 EDT [63655] editor@lmfdb LOG: duration: 2529.238 ms statement: SELECT "trace_hash", "label", "lmfdb_label", "iso", "lmfdb_iso", "iso_nlabel", "number", "lmfdb_number", "ainvs", "jinv", "conductor", "torsion", "rank", "sha", "torsion_structure", "cm", "isogeny_degrees", "nonmax_primes", "nonmax_rad", "bad_primes", "class_size" FROM "ec_curves" WHERE "sha" >= 2 AND "rank" = 2 ORDER BY "conductor", "iso_nlabel", "lmfdb_number" LIMIT 1000
2019-04-08 19:03:51.065 EDT [63997] editor@lmfdb LOG: duration: 1696.859 ms statement: FETCH FORWARD 2000 FROM "5"
2019-04-08 19:03:53.087 EDT [63846] editor@lmfdb LOG: duration: 8032.586 ms statement: SELECT "label", "g", "q", "poly", "poly_str", "angles", "ang_rank", "p_rank", "slps", "A_cnts", "A_cnts_str", "C_cnts", "C_cnts_str", "pt_cnt", "is_jac", "is_pp", "decomp", "simple_factors", "simple_distinct", "is_simp", "brauer_invs", "places", "prim_models", "is_prim", "nf", "galois_t", "galois_n", "dim1_factors", "dim2_factors", "dim3_factors", "dim4_factors", "dim5_factors", "dim1_distinct", "dim2_distinct", "dim3_distinct", "dim4_distinct", "dim5_distinct" FROM "av_fqisog" WHERE "slps" @> '["0A", "1A"]' ORDER BY "g", "q", "poly" LIMIT 1000
2019-04-08 19:03:59.724 EDT [63703] editor@lmfdb LOG: duration: 10546.235 ms statement: SELECT "label", "dim", "hecke_orbit_code", "weight" FROM "mf_newforms" WHERE "traces"[37] = 0::numeric AND "traces"[3] = 0::numeric AND "weight" = 4 AND "level" = 244 ORDER BY "analytic_conductor", "level", "char_orbit_index", "hecke_orbit" LIMIT 1000
2019-04-08 19:05:16.792 EDT [63924] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:16.797 EDT [63701] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:16.810 EDT [63789] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:16.852 EDT [63881] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:16.873 EDT [63622] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:16.925 EDT [63771] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:16.942 EDT [63928] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:16.947 EDT [63703] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:16.947 EDT [63703] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 19:05:16.969 EDT [63927] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:16.985 EDT [63601] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.001 EDT [63655] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.006 EDT [63846] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.054 EDT [63639] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.086 EDT [63806] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.097 EDT [63997] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.113 EDT [63987] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.123 EDT [63690] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.125 EDT [63925] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.163 EDT [63975] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.164 EDT [63903] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.165 EDT [63624] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.169 EDT [63977] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.180 EDT [63587] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.211 EDT [63812] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.221 EDT [63648] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.235 EDT [63729] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.266 EDT [63938] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.281 EDT [63887] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.376 EDT [63588] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.377 EDT [63964] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.387 EDT [63742] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.395 EDT [63618] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:17.411 EDT [63772] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:05:52.503 EDT [41767] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:07:03.199 EDT [50550] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:07:03.199 EDT [50550] editor@lmfdb LOG: unexpected EOF on client connection with an open transaction
2019-04-08 19:09:49.830 EDT [1897] editor@lmfdb LOG: duration: 1702.543 ms statement: FETCH FORWARD 2000 FROM "2"
2019-04-08 19:10:01.554 EDT [1897] editor@lmfdb LOG: duration: 1146.122 ms statement: FETCH FORWARD 2000 FROM "2"
2019-04-08 19:15:55.824 EDT [51172] editor@lmfdb FATAL: connection to client lost
2019-04-08 19:15:55.824 EDT [51172] editor@lmfdb STATEMENT: SELECT "trace_hash", "label", "lmfdb_label", "iso", "lmfdb_iso", "iso_nlabel", "number", "lmfdb_number", "ainvs", "jinv", "conductor", "torsion", "rank", "sha", "torsion_structure", "cm", "isogeny_degrees", "nonmax_primes", "nonmax_rad", "bad_primes", "class_size" FROM "ec_curves" ORDER BY "conductor", "iso_nlabel", "lmfdb_number"
2019-04-08 19:17:22.011 EDT [5256] editor@lmfdb LOG: duration: 42748.123 ms statement: SELECT "perfect", "abelian", "derived_group", "exponent", "name", "cyclic", "simple", "center", "maximal_subgroups", "abelian_quotient", "label", "pretty", "normal_subgroups", "solvable", "order", "clases" FROM "gps_small" ORDER BY "order", "label"
2019-04-08 19:19:42.227 EDT [63101] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-08 19:19:54.769 EDT [5400] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
(SELECT CASE WHEN waiting THEN 'waiting' WHEN state='idle' THEN 'idle' WHEN state LIKE 'idle in transaction%' THEN 'idletransaction' WHEN state='disabled' THEN 'unknown' WHEN query='<insufficient privilege>' THEN 'unknown' ELSE 'active' END AS mstate,
count(*) AS count
FROM pg_stat_activity WHERE pid != pg_backend_pid() AND datname='lmfdb'
GROUP BY CASE WHEN waiting THEN 'waiting' WHEN state='idle' THEN 'idle' WHEN state LIKE 'idle in transaction%' THEN 'idletransaction' WHEN state='disabled' THEN 'unknown' WHEN query='<insufficient privilege>' THEN 'unknown' ELSE 'active' END
) AS tmp2
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-08 19:30:09.412 EDT [11429] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-08 19:35:09.661 EDT [13862] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-08 19:40:09.283 EDT [15550] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 19:45:09.720 EDT [17248] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 19:50:09.879 EDT [18948] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 19:55:09.139 EDT [20671] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 20:00:09.612 EDT [22328] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 20:05:09.591 EDT [24090] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 20:10:09.962 EDT [25781] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
) AS tmp2
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-08 20:15:09.673 EDT [27917] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-08 20:20:09.184 EDT [29730] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 20:25:09.624 EDT [31435] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 20:30:09.171 EDT [33111] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 20:35:09.459 EDT [34934] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 20:40:09.762 EDT [36857] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 20:45:09.940 EDT [38566] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 20:50:09.923 EDT [40249] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 20:55:09.761 EDT [41936] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 21:00:09.409 EDT [43635] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 21:05:09.316 EDT [45773] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-08 21:10:09.758 EDT [47550] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 21:15:09.689 EDT [49247] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 21:20:09.202 EDT [51012] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 21:25:09.337 EDT [52795] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 21:30:09.615 EDT [54480] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 21:35:09.826 EDT [56191] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 21:40:09.409 EDT [57895] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 21:45:09.677 EDT [59599] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 21:50:10.024 EDT [61287] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
ORDER BY 1;
2019-04-08 21:55:09.521 EDT [62994] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 22:00:09.689 EDT [64649] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 22:05:09.792 EDT [1231] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
ORDER BY 1;
2019-04-08 22:10:09.340 EDT [3015] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 22:15:09.444 EDT [4726] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 22:20:09.952 EDT [6416] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 22:25:09.947 EDT [8195] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 22:30:09.566 EDT [9894] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 22:35:09.109 EDT [11596] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 22:40:09.591 EDT [13280] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 22:45:09.395 EDT [14985] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 22:50:09.280 EDT [16674] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 22:55:09.200 EDT [18366] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 23:00:09.245 EDT [20029] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 23:05:09.315 EDT [21754] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 23:10:09.313 EDT [23477] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 23:15:09.426 EDT [25170] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 23:20:09.687 EDT [26866] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 23:25:09.302 EDT [28571] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 23:30:08.963 EDT [30252] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 23:35:09.363 EDT [31944] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 23:40:09.870 EDT [33645] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 23:45:09.560 EDT [35396] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 23:50:09.891 EDT [37177] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 23:55:09.708 EDT [38883] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-08 23:59:18.532 EDT [36380] editor@lmfdb LOG: duration: 1070.724 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-08 23:59:23.148 EDT [36380] editor@lmfdb LOG: duration: 1391.634 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-08 23:59:32.313 EDT [36380] editor@lmfdb LOG: duration: 1246.341 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-08 23:59:37.524 EDT [36380] editor@lmfdb LOG: duration: 1575.070 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-08 23:59:43.404 EDT [36380] editor@lmfdb LOG: duration: 1546.427 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-08 23:59:48.572 EDT [36380] editor@lmfdb LOG: duration: 1007.517 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:00:03.538 EDT [36380] editor@lmfdb LOG: duration: 1163.042 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:02:27.465 EDT [36380] editor@lmfdb LOG: duration: 1475.227 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:02:32.738 EDT [36380] editor@lmfdb LOG: duration: 1221.017 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:02:37.294 EDT [36380] editor@lmfdb LOG: duration: 1048.408 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:02:45.411 EDT [36380] editor@lmfdb LOG: duration: 1319.529 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:03:01.376 EDT [36380] editor@lmfdb LOG: duration: 1293.667 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:03:06.264 EDT [36380] editor@lmfdb LOG: duration: 1117.699 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:03:10.636 EDT [36380] editor@lmfdb LOG: duration: 1061.021 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:03:15.070 EDT [36380] editor@lmfdb LOG: duration: 1175.717 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:03:19.925 EDT [36380] editor@lmfdb LOG: duration: 1249.110 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:03:25.010 EDT [36380] editor@lmfdb LOG: duration: 1401.760 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:03:29.915 EDT [36380] editor@lmfdb LOG: duration: 1138.428 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:03:38.409 EDT [36380] editor@lmfdb LOG: duration: 1145.765 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:03:43.088 EDT [36380] editor@lmfdb LOG: duration: 1250.304 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:03:48.175 EDT [36380] editor@lmfdb LOG: duration: 1416.695 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:03:53.487 EDT [36380] editor@lmfdb LOG: duration: 1404.944 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:03:59.259 EDT [36380] editor@lmfdb LOG: duration: 1887.023 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:04:05.597 EDT [36380] editor@lmfdb LOG: duration: 1487.639 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:04:11.165 EDT [36380] editor@lmfdb LOG: duration: 1250.196 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:04:15.871 EDT [36380] editor@lmfdb LOG: duration: 1192.228 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:04:20.886 EDT [36380] editor@lmfdb LOG: duration: 1595.273 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:04:27.018 EDT [36380] editor@lmfdb LOG: duration: 1855.219 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:04:33.441 EDT [36380] editor@lmfdb LOG: duration: 1685.833 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:04:39.122 EDT [36380] editor@lmfdb LOG: duration: 1278.130 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:04:44.339 EDT [36380] editor@lmfdb LOG: duration: 1542.773 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:04:50.082 EDT [36380] editor@lmfdb LOG: duration: 1616.807 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:04:55.966 EDT [36380] editor@lmfdb LOG: duration: 1592.587 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:05:02.561 EDT [36380] editor@lmfdb LOG: duration: 1921.074 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:08:15.874 EDT [36380] editor@lmfdb LOG: duration: 3313.404 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:08:25.463 EDT [36380] editor@lmfdb LOG: duration: 2572.166 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:08:34.542 EDT [36380] editor@lmfdb LOG: duration: 3335.240 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:08:44.919 EDT [36380] editor@lmfdb LOG: duration: 3307.886 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:08:55.143 EDT [36380] editor@lmfdb LOG: duration: 2905.227 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:09:04.689 EDT [36380] editor@lmfdb LOG: duration: 3196.362 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:09:14.553 EDT [36380] editor@lmfdb LOG: duration: 2765.740 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:09:23.784 EDT [36380] editor@lmfdb LOG: duration: 2949.058 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:09:33.175 EDT [36380] editor@lmfdb LOG: duration: 2839.807 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:09:42.512 EDT [36380] editor@lmfdb LOG: duration: 2755.706 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:09:51.672 EDT [36380] editor@lmfdb LOG: duration: 3258.712 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:10:01.960 EDT [36380] editor@lmfdb LOG: duration: 3186.003 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:11:50.641 EDT [36380] editor@lmfdb LOG: duration: 3282.832 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:12:01.344 EDT [36380] editor@lmfdb LOG: duration: 3168.273 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:12:10.543 EDT [36380] editor@lmfdb LOG: duration: 2517.314 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:12:20.193 EDT [36380] editor@lmfdb LOG: duration: 3708.460 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:12:33.080 EDT [36380] editor@lmfdb LOG: duration: 5042.222 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:12:46.217 EDT [36380] editor@lmfdb LOG: duration: 2852.926 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:12:55.515 EDT [36380] editor@lmfdb LOG: duration: 3090.171 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:13:05.419 EDT [36380] editor@lmfdb LOG: duration: 3183.300 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:13:16.710 EDT [36380] editor@lmfdb LOG: duration: 4718.007 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:13:29.781 EDT [36380] editor@lmfdb LOG: duration: 3283.026 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:13:39.564 EDT [36380] editor@lmfdb LOG: duration: 4152.825 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:13:51.760 EDT [36380] editor@lmfdb LOG: duration: 3798.895 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:14:03.329 EDT [36380] editor@lmfdb LOG: duration: 3556.092 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:14:16.328 EDT [36380] editor@lmfdb LOG: duration: 5529.454 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:14:32.046 EDT [36380] editor@lmfdb LOG: duration: 3785.570 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:14:43.871 EDT [36380] editor@lmfdb LOG: duration: 3913.573 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:14:56.282 EDT [36380] editor@lmfdb LOG: duration: 3727.352 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:20:58.727 EDT [36380] editor@lmfdb LOG: duration: 7599.173 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:21:20.240 EDT [36380] editor@lmfdb LOG: duration: 6249.301 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:21:36.576 EDT [36380] editor@lmfdb LOG: duration: 4974.423 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:21:51.848 EDT [36380] editor@lmfdb LOG: duration: 5818.228 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:22:10.831 EDT [36380] editor@lmfdb LOG: duration: 7657.706 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:22:34.062 EDT [36380] editor@lmfdb LOG: duration: 8336.277 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:23:00.614 EDT [36380] editor@lmfdb LOG: duration: 9832.689 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:23:24.233 EDT [36380] editor@lmfdb LOG: duration: 8183.513 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:23:46.926 EDT [36380] editor@lmfdb LOG: duration: 7249.806 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:24:05.853 EDT [36380] editor@lmfdb LOG: duration: 5769.936 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:24:23.324 EDT [36380] editor@lmfdb LOG: duration: 6328.673 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:24:43.189 EDT [36380] editor@lmfdb LOG: duration: 7352.447 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 00:25:03.942 EDT [36380] editor@lmfdb LOG: duration: 6552.868 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 01:27:45.227 EDT [36380] editor@lmfdb LOG: duration: 1067.590 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 01:28:43.264 EDT [36380] editor@lmfdb LOG: duration: 1043.199 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 01:28:48.372 EDT [36380] editor@lmfdb LOG: duration: 1157.337 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 01:28:53.689 EDT [36380] editor@lmfdb LOG: duration: 1211.523 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 01:28:59.269 EDT [36380] editor@lmfdb LOG: duration: 1330.137 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 01:29:05.096 EDT [36380] editor@lmfdb LOG: duration: 1490.969 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 01:29:11.064 EDT [36380] editor@lmfdb LOG: duration: 1521.757 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 01:29:18.062 EDT [36380] editor@lmfdb LOG: duration: 2384.732 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 01:29:24.546 EDT [36380] editor@lmfdb LOG: duration: 1785.028 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 01:29:31.456 EDT [36380] editor@lmfdb LOG: duration: 1924.051 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 01:29:39.037 EDT [36380] editor@lmfdb LOG: duration: 2094.115 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 01:29:46.916 EDT [36380] editor@lmfdb LOG: duration: 2424.460 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 01:30:02.396 EDT [36380] editor@lmfdb LOG: duration: 1455.815 ms statement: FETCH FORWARD 2000 FROM "1"
2019-04-09 02:04:02.513 EDT [36698] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 02:04:02.513 EDT [36697] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 02:04:02.513 EDT [36696] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 03:06:48.293 EDT [36380] editor@lmfdb LOG: duration: 66011.848 ms statement: CREATE INDEX "nf_fields_disc_rad_id_tmp" ON "nf_fields_tmp" USING btree ("disc_rad", "id") WITH (fillfactor = 100)
2019-04-09 03:08:29.715 EDT [36380] editor@lmfdb LOG: duration: 101418.544 ms statement: CREATE INDEX "nf_fields_degree_galt_disc_abs_disc_sign_tmp" ON "nf_fields_tmp" USING btree ("degree", "galt", "disc_abs", "disc_sign") WITH (fillfactor = 100)
2019-04-09 03:09:27.391 EDT [36380] editor@lmfdb LOG: duration: 57671.922 ms statement: CREATE INDEX "nf_fields_degree_galt_id_tmp" ON "nf_fields_tmp" USING btree ("degree", "galt", "id") WITH (fillfactor = 100)
2019-04-09 05:37:07.745 EDT [35008] lmfdb@lmfdb ERROR: canceling statement due to user request
2019-04-09 05:37:07.745 EDT [35008] lmfdb@lmfdb STATEMENT: SELECT c2.relname, i.indisprimary, i.indisunique, i.indisclustered, i.indisvalid, pg_catalog.pg_get_indexdef(i.indexrelid, 0, true),
pg_catalog.pg_get_constraintdef(con.oid, true), contype, condeferrable, condeferred, i.indisreplident, c2.reltablespace
FROM pg_catalog.pg_class c, pg_catalog.pg_class c2, pg_catalog.pg_index i
LEFT JOIN pg_catalog.pg_constraint con ON (conrelid = i.indrelid AND conindid = i.indexrelid AND contype IN ('p','u','x'))
WHERE c.oid = '39027901' AND c.oid = i.indrelid AND i.indexrelid = c2.oid
ORDER BY i.indisprimary DESC, i.indisunique DESC, c2.relname;
2019-04-09 05:37:22.688 EDT [35008] lmfdb@lmfdb ERROR: canceling statement due to user request
2019-04-09 05:37:22.688 EDT [35008] lmfdb@lmfdb STATEMENT: SELECT n.nspname as "Schema",
c.relname as "Name",
CASE c.relkind WHEN 'r' THEN 'table' WHEN 'v' THEN 'view' WHEN 'm' THEN 'materialized view' WHEN 'i' THEN 'index' WHEN 'S' THEN 'sequence' WHEN 's' THEN 'special' WHEN 'f' THEN 'foreign table' WHEN 'p' THEN 'table' WHEN 'I' THEN 'index' END as "Type",
pg_catalog.pg_get_userbyid(c.relowner) as "Owner",
pg_catalog.pg_size_pretty(pg_catalog.pg_table_size(c.oid)) as "Size",
pg_catalog.obj_description(c.oid, 'pg_class') as "Description"
FROM pg_catalog.pg_class c
LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
WHERE c.relkind IN ('r','p','v','m','S','f','')
AND n.nspname <> 'pg_catalog'
AND n.nspname <> 'information_schema'
AND n.nspname !~ '^pg_toast'
AND pg_catalog.pg_table_is_visible(c.oid)
ORDER BY 1,2;
2019-04-09 05:37:51.434 EDT [35025] lmfdb@lmfdb ERROR: canceling statement due to user request
2019-04-09 05:37:51.434 EDT [35025] lmfdb@lmfdb STATEMENT: SELECT n.nspname as "Schema",
c.relname as "Name",
CASE c.relkind WHEN 'r' THEN 'table' WHEN 'v' THEN 'view' WHEN 'm' THEN 'materialized view' WHEN 'i' THEN 'index' WHEN 'S' THEN 'sequence' WHEN 's' THEN 'special' WHEN 'f' THEN 'foreign table' WHEN 'p' THEN 'table' WHEN 'I' THEN 'index' END as "Type",
pg_catalog.pg_get_userbyid(c.relowner) as "Owner",
pg_catalog.pg_size_pretty(pg_catalog.pg_table_size(c.oid)) as "Size",
pg_catalog.obj_description(c.oid, 'pg_class') as "Description"
FROM pg_catalog.pg_class c
LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
WHERE c.relkind IN ('r','p','v','m','S','f','')
AND n.nspname <> 'pg_catalog'
AND n.nspname <> 'information_schema'
AND n.nspname !~ '^pg_toast'
AND pg_catalog.pg_table_is_visible(c.oid)
ORDER BY 1,2;
2019-04-09 05:38:56.474 EDT [52194] webserver@lmfdb ERROR: canceling statement due to statement timeout
2019-04-09 05:38:56.474 EDT [52194] webserver@lmfdb STATEMENT: SELECT "label", "coeffs", "degree", "r2", "cm", "iso_number", "disc_abs", "disc_sign", "disc_rad", "ramps", "galt", "class_number", "class_group", "used_grh", "rd" FROM "nf_fields" WHERE "degree" = 2 ORDER BY "degree", "disc_abs", "disc_sign", "iso_number" LIMIT 50
2019-04-09 07:00:06.857 EDT [52184] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 07:00:06.862 EDT [52207] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 07:00:06.862 EDT [52203] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 07:00:06.865 EDT [52201] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 07:00:06.865 EDT [52204] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 07:00:06.866 EDT [52202] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 07:00:06.868 EDT [52192] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 07:00:06.869 EDT [52199] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 07:00:06.869 EDT [52200] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 07:00:06.872 EDT [52190] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 07:00:09.316 EDT [63618] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-09 07:05:09.471 EDT [344] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-09 07:10:09.748 EDT [2609] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
ORDER BY 1;
2019-04-09 07:15:09.100 EDT [4454] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
(VALUES ('active'),('waiting'),('idle'),('idletransaction'),('unknown')) AS tmp(mstate)
LEFT JOIN
(SELECT CASE WHEN waiting THEN 'waiting' WHEN state='idle' THEN 'idle' WHEN state LIKE 'idle in transaction%' THEN 'idletransaction' WHEN state='disabled' THEN 'unknown' WHEN query='<insufficient privilege>' THEN 'unknown' ELSE 'active' END AS mstate,
count(*) AS count
FROM pg_stat_activity WHERE pid != pg_backend_pid() AND datname='lmfdb'
GROUP BY CASE WHEN waiting THEN 'waiting' WHEN state='idle' THEN 'idle' WHEN state LIKE 'idle in transaction%' THEN 'idletransaction' WHEN state='disabled' THEN 'unknown' WHEN query='<insufficient privilege>' THEN 'unknown' ELSE 'active' END
) AS tmp2
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-09 07:20:09.507 EDT [6170] postgres@template1 ERROR: could not open directory "pg_xlog": No such file or directory
2019-04-09 07:22:34.362 EDT [63805] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 07:22:34.369 EDT [63796] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 07:22:57.983 EDT [63795] webserver@lmfdb ERROR: canceling statement due to statement timeout
2019-04-09 07:22:57.983 EDT [63795] webserver@lmfdb STATEMENT: SELECT "label", "coeffs", "degree", "r2", "cm", "iso_number", "disc_abs", "disc_sign", "disc_rad", "ramps", "galt", "class_number", "class_group", "used_grh", "rd", "zk", "units", "reg", "subs", "unitsGmodule", "unitsType", "res", "loc_algebras" FROM "nf_fields" JOIN "nf_fields_extras" USING (id) WHERE "label" = '4.0.15376.1' LIMIT 1
2019-04-09 07:22:58.392 EDT [63795] webserver@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 07:24:03.502 EDT [7783] webserver@lmfdb ERROR: canceling statement due to statement timeout
2019-04-09 07:24:03.502 EDT [7783] webserver@lmfdb STATEMENT: SELECT "label", "coeffs", "degree", "r2", "cm", "iso_number", "disc_abs", "disc_sign", "disc_rad", "ramps", "galt", "class_number", "class_group", "used_grh", "rd", "zk", "units", "reg", "subs", "unitsGmodule", "unitsType", "res", "loc_algebras" FROM "nf_fields" JOIN "nf_fields_extras" USING (id) WHERE "label" = '4.0.15376.1' LIMIT 1
2019-04-09 07:24:49.257 EDT [7787] webserver@lmfdb ERROR: canceling statement due to statement timeout
2019-04-09 07:24:49.257 EDT [7787] webserver@lmfdb STATEMENT: SELECT "label", "coeffs", "degree", "r2", "cm", "iso_number", "disc_abs", "disc_sign", "disc_rad", "ramps", "galt", "class_number", "class_group", "used_grh", "rd", "zk", "units", "reg", "subs", "unitsGmodule", "unitsType", "res", "loc_algebras" FROM "nf_fields" JOIN "nf_fields_extras" USING (id) WHERE "label" = '5.1.1244084.1' LIMIT 1
2019-04-09 07:34:53.938 EDT [7786] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [7776] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [7782] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [7778] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [7784] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [35025] lmfdb@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [34284] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [49500] editor@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [36380] editor@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [36380] editor@lmfdb STATEMENT: ALTER TABLE "nf_fields" RENAME TO "nf_fields_old1"
2019-04-09 07:34:53.938 EDT [3981] editor@lmfdb FATAL: terminating connection due to administrator command at character 252
2019-04-09 07:34:53.938 EDT [3981] editor@lmfdb STATEMENT: SELECT "label", "coeffs", "degree", "r2", "cm", "iso_number", "disc_abs", "disc_sign", "disc_rad", "ramps", "galt", "class_number", "class_group", "used_grh", "rd", "zk", "units", "reg", "subs", "unitsGmodule", "unitsType", "res", "loc_algebras" FROM "nf_fields" JOIN "nf_fields_extras" USING (id) LIMIT 1
2019-04-09 07:34:53.938 EDT [34287] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [34286] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [1897] editor@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [34283] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [34282] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [57351] lmfdb@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [34706] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [14706] editor@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [7320] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [7321] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [7318] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [48451] editor@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [7781] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [23139] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.938 EDT [7785] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.939 EDT [61302] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.939 EDT [61296] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.939 EDT [7780] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.941 EDT [20786] lmfdb@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.944 EDT [61300] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.944 EDT [7777] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.944 EDT [7779] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.945 EDT [53429] editor@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.945 EDT [59644] editor@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.946 EDT [7319] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.946 EDT [23140] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.949 EDT [7317] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.950 EDT [22592] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.950 EDT [35121] lmfdb@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.950 EDT [36248] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.950 EDT [34435] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.950 EDT [36252] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.950 EDT [23127] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.950 EDT [36020] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.951 EDT [36021] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.952 EDT [36023] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.952 EDT [22590] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.952 EDT [36022] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.952 EDT [61301] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.952 EDT [56508] lmfdb@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.952 EDT [15850] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.953 EDT [1911] editor@lmfdb FATAL: terminating connection due to administrator command at character 203
2019-04-09 07:34:53.953 EDT [1911] editor@lmfdb STATEMENT: DECLARE "2" CURSOR WITH HOLD FOR SELECT "label", "coeffs", "degree", "r2", "cm", "iso_number", "disc_abs", "disc_sign", "disc_rad", "ramps", "galt", "class_number", "class_group", "used_grh", "rd" FROM "nf_fields" ORDER BY "degree", "disc_abs", "disc_sign", "iso_number"
2019-04-09 07:34:53.953 EDT [34405] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.953 EDT [22587] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.953 EDT [22591] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.953 EDT [35132] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.954 EDT [61291] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.956 EDT [63051] editor@lmfdb FATAL: terminating connection due to administrator command at character 203
2019-04-09 07:34:53.956 EDT [63051] editor@lmfdb STATEMENT: DECLARE "1" CURSOR WITH HOLD FOR SELECT "label", "coeffs", "degree", "r2", "cm", "iso_number", "disc_abs", "disc_sign", "disc_rad", "ramps", "galt", "class_number", "class_group", "used_grh", "rd" FROM "nf_fields" ORDER BY "degree", "disc_abs", "disc_sign", "iso_number"
2019-04-09 07:34:53.956 EDT [22593] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.957 EDT [36249] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.961 EDT [36255] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.961 EDT [36189] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.963 EDT [36024] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.968 EDT [36250] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.969 EDT [23138] webserver@lmfdb FATAL: terminating connection due to administrator command
2019-04-09 07:34:53.973 EDT [1265] LOG: worker process: logical replication launcher (PID 1391) exited with exit code 1
2019-04-09 07:35:02.697 EDT [11532] postgres@template1 FATAL: the database system is shutting down
2019-04-09 07:35:02.844 EDT [11541] postgres@template1 FATAL: the database system is shutting down
2019-04-09 07:35:03.093 EDT [11560] postgres@template1 FATAL: the database system is shutting down
2019-04-09 07:35:03.247 EDT [11562] postgres@template1 FATAL: the database system is shutting down
2019-04-09 07:35:03.507 EDT [11583] postgres@template1 FATAL: the database system is shutting down
2019-04-09 07:35:03.656 EDT [11592] postgres@template1 FATAL: the database system is shutting down
2019-04-09 07:35:04.364 EDT [11664] postgres@template1 FATAL: the database system is shutting down
2019-04-09 07:35:04.517 EDT [11666] postgres@template1 FATAL: the database system is shutting down
2019-04-09 07:35:08.747 EDT [11940] postgres@template1 FATAL: the database system is shutting down
2019-04-09 07:35:08.796 EDT [11941] editor@lmfdb FATAL: the database system is shutting down
2019-04-09 07:35:08.799 EDT [11943] editor@lmfdb FATAL: the database system is shutting down
2019-04-09 07:35:08.895 EDT [11944] postgres@template1 FATAL: the database system is shutting down
2019-04-09 07:35:10.434 EDT [1385] LOG: shutting down
2019-04-09 07:35:19.643 EDT [1265] LOG: database system is shut down
2019-04-09 07:35:19.951 EDT [11967] LOG: listening on IPv4 address "0.0.0.0", port 5432
2019-04-09 07:35:19.951 EDT [11967] LOG: listening on IPv6 address "::", port 5432
2019-04-09 07:35:19.993 EDT [11967] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2019-04-09 07:35:21.146 EDT [11977] LOG: database system was shut down at 2019-04-09 07:35:11 EDT
2019-04-09 07:35:21.222 EDT [11967] LOG: database system is ready to accept connections
2019-04-09 07:35:21.755 EDT [11989] [unknown]@[unknown] LOG: incomplete startup packet
2019-04-09 07:36:18.116 EDT [13222] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 09:18:57.105 EDT [16577] webserver@lmfdb STATEMENT: INSERT INTO kwl_locks (id, timestamp, username) VALUES ('mf.base_change', '2019-04-09T13:18:57.105495'::timestamp, 'jvoight')
2019-04-09 11:12:17.344 EDT [14555] webserver@lmfdb STATEMENT: SELECT username, timestamp FROM kwl_locks WHERE id = 'dq.cmf.extent' AND timestamp >= '2019-04-09T15:02:17.343204'::timestamp LIMIT 1
2019-04-09 11:12:17.346 EDT [14555] webserver@lmfdb ERROR: permission denied for relation kwl_locks
2019-04-09 11:12:17.346 EDT [14555] webserver@lmfdb STATEMENT: INSERT INTO kwl_locks (id, timestamp, username) VALUES ('dq.cmf.extent', '2019-04-09T15:12:17.345509'::timestamp, 'jvoight')
2019-04-09 11:32:36.688 EDT [12533] webserver@lmfdb STATEMENT: INSERT INTO kwl_locks (id, timestamp, username) VALUES ('curve.highergenus.aut.generatingvector', '2019-04-09T15:32:36.688305'::timestamp, 'jvoight')
2019-04-09 11:32:51.647 EDT [16577] webserver@lmfdb ERROR: permission denied for relation kwl_locks
2019-04-09 11:32:51.647 EDT [16577] webserver@lmfdb STATEMENT: SELECT username, timestamp FROM kwl_locks WHERE id = 'ag.hyperelliptic_curve' AND timestamp >= '2019-04-09T15:22:51.647228'::timestamp LIMIT 1
2019-04-09 11:32:51.648 EDT [16577] webserver@lmfdb ERROR: permission denied for relation kwl_locks
2019-04-09 11:32:51.648 EDT [16577] webserver@lmfdb STATEMENT: INSERT INTO kwl_locks (id, timestamp, username) VALUES ('ag.hyperelliptic_curve', '2019-04-09T15:32:51.648194'::timestamp, 'jvoight')
2019-04-09 11:33:29.647 EDT [12533] webserver@lmfdb LOG: duration: 4618.692 ms statement: SELECT "ndim", "jacobian_decomp", "cc", "full_auto", "passport_label", "group", "signH", "label", "hyp_involution", "full_label", "eqn", "cinv", "hyperelliptic", "gen_vectors", "total_label", "g0", "dim", "group_order", "cyclic_trigonal", "r", "signature", "genus", "con", "braid", "topological", "realcc" FROM "hgcwa_passports" WHERE "passport_label" = '15.14-1.0.2-2-2-2-2-2-2-2.1' ORDER BY "genus", "dim", "cc"
2019-04-09 13:03:05.503 EDT [15192] webserver@lmfdb ERROR: permission denied for relation kwl_locks
2019-04-09 13:03:05.503 EDT [15192] webserver@lmfdb STATEMENT: SELECT username, timestamp FROM kwl_locks WHERE id = 'lfunction.analytic_rank' AND timestamp >= '2019-04-09T16:53:05.502453'::timestamp LIMIT 1
2019-04-09 13:03:05.504 EDT [15192] webserver@lmfdb ERROR: permission denied for relation kwl_locks
2019-04-09 13:03:05.504 EDT [15192] webserver@lmfdb STATEMENT: INSERT INTO kwl_locks (id, timestamp, username) VALUES ('lfunction.analytic_rank', '2019-04-09T17:03:05.504195'::timestamp, 'drew')
2019-04-09 13:04:52.531 EDT [13353] webserver@lmfdb ERROR: permission denied for relation kwl_locks
2019-04-09 13:04:52.531 EDT [13353] webserver@lmfdb STATEMENT: SELECT username, timestamp FROM kwl_locks WHERE id = 'test.newname3.1554829492492658.comment' AND timestamp >= '2019-04-09T16:54:52.531550'::timestamp LIMIT 1
2019-04-09 13:04:52.532 EDT [13353] webserver@lmfdb ERROR: permission denied for relation kwl_locks
2019-04-09 13:04:52.532 EDT [13353] webserver@lmfdb STATEMENT: INSERT INTO kwl_locks (id, timestamp, username) VALUES ('test.newname3.1554829492492658.comment', '2019-04-09T17:04:52.532587'::timestamp, 'drew')
2019-04-09 13:09:03.191 EDT [13353] webserver@lmfdb ERROR: permission denied for relation kwl_locks
2019-04-09 13:09:03.191 EDT [13353] webserver@lmfdb STATEMENT: INSERT INTO kwl_locks (id, timestamp, username) VALUES ('test.newname3.1554829492492658.comment', '2019-04-09T17:09:03.191086'::timestamp, 'drew')
2019-04-09 13:09:13.536 EDT [12533] webserver@lmfdb ERROR: permission denied for relation kwl_locks
2019-04-09 13:09:13.536 EDT [12533] webserver@lmfdb STATEMENT: SELECT username, timestamp FROM kwl_locks WHERE id = 'test.newname3.1554829492492658.comment' AND timestamp >= '2019-04-09T16:59:13.535851'::timestamp LIMIT 1
2019-04-09 13:09:13.537 EDT [12533] webserver@lmfdb ERROR: permission denied for relation kwl_locks
2019-04-09 13:09:13.537 EDT [12533] webserver@lmfdb STATEMENT: INSERT INTO kwl_locks (id, timestamp, username) VALUES ('test.newname3.1554829492492658.comment', '2019-04-09T17:09:13.536810'::timestamp, 'drew')
2019-04-09 13:09:24.066 EDT [16577] webserver@lmfdb ERROR: permission denied for relation kwl_locks
2019-04-09 13:09:24.066 EDT [16577] webserver@lmfdb STATEMENT: SELECT username, timestamp FROM kwl_locks WHERE id = 'test.newname3.1554829492492658.comment' AND timestamp >= '2019-04-09T16:59:24.065641'::timestamp LIMIT 1
2019-04-09 13:09:24.067 EDT [16577] webserver@lmfdb ERROR: permission denied for relation kwl_locks
2019-04-09 13:09:24.067 EDT [16577] webserver@lmfdb STATEMENT: INSERT INTO kwl_locks (id, timestamp, username) VALUES ('test.newname3.1554829492492658.comment', '2019-04-09T17:09:24.066819'::timestamp, 'drew')
2019-04-09 13:45:33.206 EDT [12533] webserver@lmfdb STATEMENT: INSERT INTO kwl_locks (id, timestamp, username) VALUES ('lfunction.conductor', '2019-04-09T17:45:33.206357'::timestamp, 'drew')
(VALUES ('active'),('waiting'),('idle'),('idletransaction'),('unknown')) AS tmp(mstate)
LEFT JOIN
(SELECT CASE WHEN waiting THEN 'waiting' WHEN state='idle' THEN 'idle' WHEN state LIKE 'idle in transaction%' THEN 'idletransaction' WHEN state='disabled' THEN 'unknown' WHEN query='<insufficient privilege>' THEN 'unknown' ELSE 'active' END AS mstate,
count(*) AS count
FROM pg_stat_activity WHERE pid != pg_backend_pid() AND datname='lmfdb'
GROUP BY CASE WHEN waiting THEN 'waiting' WHEN state='idle' THEN 'idle' WHEN state LIKE 'idle in transaction%' THEN 'idletransaction' WHEN state='disabled' THEN 'unknown' WHEN query='<insufficient privilege>' THEN 'unknown' ELSE 'active' END
) AS tmp2
ON tmp.mstate=tmp2.mstate
ORDER BY 1;
2019-04-09 17:55:03.829 EDT [27085] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 17:56:09.597 EDT [30420] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 17:56:17.035 EDT [31684] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
2019-04-09 17:56:19.309 EDT [30736] editor@lmfdb LOG: could not receive data from client: Connection reset by peer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment