newbie_business_analyst nologin;
Is replicated, so it would block logins on both servers.
Thanks,
Andomar
before and after the update.
Is there a way to have Postgres explain why the outer query drops a row even
though the query plan does not show a filter?
Cheers,
Andomar
ange for presence of confidential information in the disclosed bytes, but
they seem unlikely. (CVE-2015-5288)
---
The "crypt" call is hardcoded in legacy code that hasn't been recompiled in
years. Are there ways to keep the old code running against a newer Postgres
version?
Kind regards,
An
itting
up data and logs mean that there is less chance the disk controller will
cause data writes to interfere with log files.
Kind regards,
Andomar
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mail
ime comes where the few milliseconds matter, it is easy to add
connection pooling without changing a single line of code. Postgres offers
pgbouncer and pgpool for that job, but if DBCP can do it, that’s fine too.
Kind regards,
Andomar
--
Sent via pgsql-general mailing list (pgsql-general@
>
> If I have taken any backup successfully through pg_dump? How can I restore
> this pg_dump(Sql file) without use of pg_restore.
>
You can send the file to psql, the command line client:
psql yourdb < yourbackup.sql
Or:
cat yourbackup.sql | psql yourdb
Kind r
oks like the Postgres
logging collector somehow misses out on the stream of messages.
Kind regards,
Andomar
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
tried
various settings but none result in a regular Postgres log file. The Postgres
settings for systemd can be found here:
/usr/lib/systemd/system/postgresql.service
Is there a way to let Postgres do its own logging when it is started by systemd?
Kind regards,
Andomar
P.S. Trying to figure
tings where name =
'max_connections'" shows that the setting already is 125. So the
warning is confusing because a restart would not change anything.
Kind regards,
Andomar
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
guration file.
Is this behavior "by design", or should Postgres not give an error under
the above circumstances?
Kind Regards,
Andomar
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
by through pgbouncer, or
if we need a separate open port on the database server just for replication.
Cheers,
Andomar
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
I'm doubtful. Why do you think you need such a capability?
For simplicity. If I can replicate through pgbouncer, I'll need only
one open port on the machine. Postgres would just listen on localhost.
If not, I'll have to make Postgres listen on an interface on a different
p
replicate over a connection through pgbouncer?
Kind regards,
Andomar
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
t;cnt" now does exist.
Kind regards,
Andomar
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
raise notice 'deleted % rows', num_rows;
exit when num_rows = 0;
end loop;
end;$_$;
This deletes rows with an id smaller than 500 in chunks of 100.
Kind regards,
Andomar
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to yo
SELECT COALESCE(ts1.user_id, ts2,user_id, ts3.user_id) AS user_id,
That should probably be ts2 DOT user_id.
Cheers,
Andomar
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
was an error accessing the disk? How is the
filesystem that contains your PGDATA directory mounted?
Kind regards,
Andomar
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
9.4 -> 9.3 downgrade for now.
For anyone else finding this thread, we are running CentOS 6.5 with
kernel 2.6.32 (which was released in Dec 2009.)
Cheers,
Andomar
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Would you be able to get a stack trace of a backend that's holding an
extension lock? Or maybe perf would provide some insight.
The outage occurred again but briefer. There were no ExclusiveLock
messages, presumably because the timeout for logging locks was not
exceeded. But all available c
has constant and considerable load of small writes. The
pg_activity tool shows 300 IOPs sustained (it claims max IPs above
11000.) Postgres 9.3 had a comparable pgfree/s.
Would you know a good resource to get more knowledgeable about pgfree,
pgpin, pgsteal?
Kind regards,
Andomar
--
S
hey're sometimes
zero for more than half an hour, so they don't seem related to checkpoints.
Kind regards,
Andomar
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
but there does seem to be a peak in
I/O requests around the CPU spikes.
Is a page split by nature a synchronous I/O activity? And do the other
connections wait in some kind of CPU intensive form (like a spinlock?)
Kind regards,
Andomar
--
Sent via pgsql-general mailing list (pgsql-genera
current fillfactor of a table and its indices?
Kind regards,
Andomar
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
o approach this issue are welcome.
Thanks for your time,
Andomar
P.S. The upgrade was done with pg_dump. So the database was converted
to SQL and then imported into 9.4.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.post
rry about.
Well that was just an example query, but checking a realistic query on a
test machine shows 15ms spent on query analysis. For 200 queries/sec
that would keep around 3 CPU's busy, which is what we saw. I will try to
verify that using the log_planner_stats option.
Cheers,
Ando
piling around 200 queries a second on our production machine. Is that
even possible?
Cheers,
Andomar
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
tatistics table (pg_statistics)?
Thanks for any answers or pointers,
Andomar
P.S. I've asked this question on StackExchange
http://dba.stackexchange.com/questions/86620/monitoring-the-postgres-query-parser/86626#86626
but I'm looking for more specific information.
--
Sent via p
27 matches
Mail list logo
