You can leave authentication to something else. For example authenticate
the users by having them connect to pgBouncer first.
-Joseph
On Fri, Dec 16, 2016 at 11:17 AM, Andomar wrote:
> We run a master server and a hot standby server. Reporting users login to
> the standby server to run long que
On Mon, Aug 1, 2016 at 5:21 PM, Jeff Janes wrote:
> On Mon, Aug 1, 2016 at 1:32 PM, John McKown
> wrote:
> > On Mon, Aug 1, 2016 at 2:49 PM, Jeff Janes wrote:
> >>
> >> On Mon, Aug 1, 2016 at 11:40 AM, Joseph Kregloh <
> jkreg...@sproutloud.com>
> >
Hi,
Is there a way to force the user being sent to LDAP?
For example I have the following entry in my pg_hba.conf file:
hostapdb apuser 10.0.20.1/22 ldap
ldapserver="389-ds1.sl.com:389" ldapbasedn="dc=sl,dc=com"
- I will be connecting as apuser.
- I will supply my
On Tue, May 31, 2016 at 4:12 PM, Alvaro Herrera
wrote:
> Joseph Kregloh wrote:
> > It is my understanding that if PostgeSQL has log shipping enabled, if for
> > whatever reason it cannot ship the file the master server will hold it.
> But
> > for how long?
>
>
It is my understanding that if PostgeSQL has log shipping enabled, if for
whatever reason it cannot ship the file the master server will hold it. But
for how long?
Secondly, I have 2 servers I ship log files to using the following script:
#!/usr/local/bin/bash
# Slave 1
rsync -a $1 pgi@192.168.1
On Thu, Oct 1, 2015 at 5:51 PM, Jim Nasby wrote:
> On 10/1/15 8:50 AM, Joseph Kregloh wrote:
>
>> In my testing with pgbench I actually saw a decrease in performance with
>> a ZIL enabled. I ended up just keeping the L2ARC and dropping the. ZIL
>> will not provide you w
stalled on the machine? How did you set up PG? (PG
> defaults are historically horrible for higher-RAM machines)
>
>
In my testing with pgbench I actually saw a decrease in performance with a
ZIL enabled. I ended up just keeping the L2ARC and dropping the. ZIL will
not provide you wit
to continue using the start_backup , rsync and
> stop_backup. ;(
>
>
You can always move the folder out of there. Depending on the version of
PostgreSQL different steps need to be take. If I remember correctly for
version 9.3 you can move the symlink to point to the new directory. Pre 9.3
you need to move the symlink and the pointer inside the pg tables.
-Joseph Kregloh
> Thanks!
>
than a
> factor of 5 (from memory) in terms of throughput.
>
> Considering the time to move heads between tracks and rotational latency
> (caused by not reading sequential blocks on the same track). There are
> other complications, which I have glossed over!
>
>
It can go even
On Thu, Aug 20, 2015 at 9:50 AM, Laurent Laborde
wrote:
> Friendly greetings !
>
> I'm wondering if anyone tried the following hot backup process, and if it
> works :
> pg_start_backup()
> zfs snapshop
> pg_stop_backup()
>
> copy the snapshot to the backup server.
>
That is how I currently handl
built the same and not every PostgreSQL server is used the same, to tune
according to the machine and the usage of the server.
Thanks,
-Joseph Kregloh
On Tue, Aug 18, 2015 at 5:52 AM, Sachin Srivastava
wrote:
> Hi,
>
> If my system RAM is 50 GB then how can I tune my database server withou
and set
recovery_target_timeline to latest
5. Start slave B, then start slave A now master.
So far everything seems to work.
-Joseph Kregloh
On Tue, Jul 21, 2015 at 2:37 PM, William Dunn wrote:
> As I am aware, you would have two options depending on your configuration:
>
>1. C
>
>
Jails work, but in this case it would be more trouble. If you had it in a
jail already then that would be different story.
> c) Somehow modify the ports options so each versions binary is installed
> separately. I have no idea how to do it, maybe need to ask this on the
> FreeBSD mailing list.
>
This I explained above.
-Joseph Kregloh
ed to start replicating to the other slave the moment I trigger it's
promotion?
Thanks,
-Joseph Kregloh
On Thu, Jul 2, 2015 at 11:50 AM, Vick Khera wrote:
>
> On Thu, Jul 2, 2015 at 10:56 AM, Joseph Kregloh
> wrote:
>
>> With my dataset I have been able to take advantage of the L2ARC.
>> Currently using about 80GB on ARC and 260GB on L2ARC. With the ARC
>> currentl
On Thu, Jul 2, 2015 at 9:35 AM, Vick Khera wrote:
>
> On Wed, Jul 1, 2015 at 5:07 PM, Joseph Kregloh
> wrote:
>
>> We recently built a new server for our Production database. The machine
>> is top of the line with 128GB of RAM, dual E5-2650. We also included NVME
>
with
it enabled and disabled.
I've included a copy of one of the tests done.
Thanks,
-Joseph Kregloh
You will want to setup your replication user to connect to PostgreSQL
directly. Going through pgBouncer is asking for trouble.
-Joseph Kregloh
On Wed, Apr 22, 2015 at 5:30 PM, John R Pierce wrote:
> On 4/22/2015 11:37 AM, Joseph Kregloh wrote:
>
>> I have successfully setup LDAP and setup simple authentication using
>> simple bind. This was my test case. Now I need to move to the next lever
>> which would be se
the query,
everything else I can hardcode into the search filter.
Would an ldapurl be better here? But again how will I pass the uid to the
ldapurl?
Thanks,
-Joseph Kregloh
backup of one day.
Thanks,
-Joseph Kregloh
On Wed, Mar 11, 2015 at 9:26 AM, Stéphane Schildknecht <
stephane.schildkne...@postgres.fr> wrote:
> Hello,
>
> On 11/03/2015 11:54, Robert Inder wrote:
> > We are developing a new software system which is now used by a number
>
On Wed, Mar 11, 2015 at 9:55 AM, Andrew Sullivan
wrote:
> On Wed, Mar 11, 2015 at 09:40:09AM -0400, Joseph Kregloh wrote:
> > Have you looked into Barman? http://www.pgbarman.org/ It does what you
> > want. You can take a full daily backup and it keeps track of the WAL
> file
could do a PITR up to a
month in the past.
Thanks,
-Joseph Kregloh
On Mon, Jan 12, 2015 at 5:16 PM, Antony Gelberg
wrote:
> On Mon, Jan 12, 2015 at 7:08 PM, Adrian Klaver
> wrote:
> >
> > On 01/12/2015 08:40 AM, Antony Gelberg wrote:
> >>
> >> On Mon, Ja
The way I would do it is to setup pgBouncer and control the user access
from there. Not to mention the connection pooling gains you would get from
pgBouncer itself. The simples way is to setup all of the users to connect
through pgBouncer, then the admin users connect to the Postgresql port
directl
On Mon, Dec 15, 2014 at 7:12 PM, Sameer Kumar
wrote:
>
> On 16 Dec 2014 01:13, "Joseph Kregloh" wrote:
> >
> > Hello,
> >
> > I have a master multi slave streaming replication setup. One master and
> two slaves. I need to do some maintenance on on
On Mon, Dec 15, 2014 at 2:18 PM, Patrick Krecker
wrote:
> On Mon, Dec 15, 2014 at 10:29 AM, Joseph Kregloh
> wrote:
> >
> >
> > On Mon, Dec 15, 2014 at 12:59 PM, Patrick Krecker
> > wrote:
> >>
> >> On Mon, Dec 15, 2014 at 9:12 AM, Joseph
On Mon, Dec 15, 2014 at 12:59 PM, Patrick Krecker
wrote:
> On Mon, Dec 15, 2014 at 9:12 AM, Joseph Kregloh
> wrote:
> > Hello,
> >
> > I have a master multi slave streaming replication setup. One master and
> two
> > slaves. I need to do some maintenance o
that the slave in question is not serving any connections.
>From what I remember emptying out the archive_command would pause log
shipping. Can the same be done by issuing a pg_stop_backup()?
Thanks,
-Joseph Kregloh
I use Zabbix a lot. There is very nice template for Postgres
http://pg-monz.github.io/pg_monz/index-en.html
On Sun, Dec 14, 2014 at 12:13 PM, Tim Smith
wrote:
> Try http://brendangregg.com/
>
> Lots of great tidbits there from a guy who really knows his performance
> stuff (ex-Sun, now Netflix)
Currently I use FreeBSD 10 with ZFS filesystem for our Production database.
Speed wise it's fine, i'm sure other filesystems could be faster, even
though we have never compared it with other filesystems. The reason we do
ZFS is to take advantage of the data compression and snapshots. It is very
eas
l be set to 'on' and left that way.
>
>
Yep, I run version 9.3 on all the environments.
>
> Joseph Kregloh writes:
>
> > On Fri, Aug 22, 2014 at 2:21 PM, Jerry Sievers
> wrote:
> >
> > Joseph Kregloh writes:
> >
> > >
On Fri, Aug 22, 2014 at 2:21 PM, Jerry Sievers
wrote:
> Joseph Kregloh writes:
>
> > Hi,
> >
> > Currently I am doing asynchronous replication from master to
> > slave. Now if I restart the slave it will fall out of sync with the
> > master. Is there a correc
up.
I apologize if this question has already been asked. I did some searching
beforehand.
Thanks,
-Joseph Kregloh
Why don't you try using Barman? It allows you to take snapshots and do
PITR. Not to mention you can use it as it's intended purpose as a backup
engine.
-Joseph
On Thu, Aug 14, 2014 at 1:53 PM, Bill Mitchell wrote:
> We are running our own Postgres server on AWS as well (since amazon RDS
> does
> This will be fixed in the next 9.3 minor release by throwing ane error
> for non-existent tablespace directores.
>
>
Awesome! I have already upgraded my dev, stage, preprod, and production
environments to 9.3. However I do have some snapshots that I can test with.
> --
> Bruce Momjian
I browsed through messages related to this issue? I have a few questions to
the OP. How did you upgrade? Did you reindex the database? Try reindexdb
and see what happens. If you used pg_upgrade, you need to reindex. I did
pg_upgrade on my production db and it wasn't any faster on 9.3 than on 9.0,
u
9AM -0500, Joseph Kregloh wrote:
> >
> >
> >
> > Right. I know there were multiple issue with this upgrade, jails
> > probably being the biggest, but a new one I had never heard is that
> _if_
> > you are placing your tablespaces in the PGDATA directo
Right. I know there were multiple issue with this upgrade, jails
> probably being the biggest, but a new one I had never heard is that _if_
> you are placing your tablespaces in the PGDATA directory, and you are
> upgrading from pre-9.2, if you rename the old data directory, you also
> need to sta
On Fri, Jan 10, 2014 at 11:53 AM, Adrian Klaver wrote:
> On 01/10/2014 08:40 AM, Joseph Kregloh wrote:
>
>> Just as a followup to this. The process that I am using to do the
>> upgrade is as follows:
>>
>> 1. Install Postgres 9.3 in /opt dir.
>> 2. I
location as the documentation shows. But I
haven't experimented with that scenario yet.
-Joseph
On Tue, Dec 31, 2013 at 7:06 PM, Adrian Klaver wrote:
> On 12/31/2013 04:03 PM, Joseph Kregloh wrote:
>
>>
>>
>>
>> On Tue, Dec 31, 2013 at 5:08 PM, Adrian Klaver > &
On Tue, Dec 31, 2013 at 5:08 PM, Adrian Klaver wrote:
> On 12/31/2013 01:31 PM, Joseph Kregloh wrote:
>
>>
>> ERROR: relation "sys_errors" does not exist
>> LINE 1: SELECT * FROM sys_errors ORD
>
> So you have not upgraded the tablespaces. What is important to remember is
>> Postgres uses numbers to keep track of relations. Part of the upgrade
>> process involves changing the numbers that point at relations. By manually
>> dropping a 9.0 tablespace into a 9.3 data directory you have broke
>
>
>> ERROR: relation "sys_errors" does not exist
>> LINE 1: SELECT * FROM sys_errors ORDER BY created_ts DESC LIMIT 100;
>>^
>> ** Error **
>>
>> ERROR: relation "sys_errors" does not exist
>> SQL state: 42P01
>> Character: 15
>>
>
> sys_errors is a table
I did a bit more experimenting today. First test:
/opt/bin/pg_upgrade -d /usr/local/pgsql/data -D /usr/local/pgsql_93/data/
-b /usr/local/bin/ -B /opt/bin/ -p 5452 -P 5451
It completes successfully, however I still have the user defined
tablespaces inside the 9.0 data folder. So I manually moved
I used Site5 for the longest, maybe until 5 or 6 years ago. The problem
with shared hosting is that many times they are unwilling to install
software because they don't really know what it does or they don't want to
support it. Basically they don't want to affect the rest of the server just
by help
>
> FYI, some testing showed that playing around with spclocation in
> pg_tablespace is not recommended.
Do you happen to have more information about this? Because it would
actually solve all my problems by moving the user created tablespaces out
of the /data directory. But I would like more info
>
>
> Postgres is going to /usr/local/pgsql/data/drupal_dbspace/ to look for
> the 9.0 files instead of /usr/local/pgsql_90/data/drupal_dbspace/ and is
> trying to copy them as 9.3 versions into the new default location which has
> the same path. Since the new
> /usr/local/pgsql/data/drupal_dbspac
>
>
>> So how are you moving the 9.0 directory?
>
Just using a mv command like below:
mv /usr/local/pgsql/data /usr/local/pgsql_90/data
Then I recreated the symlinks in /pg_tbspc to point to the new directory
path.
What does a listing for that directory look like after the move?
>
[pgsql@postgr
>
> Here is the message on --hackers that explains the above:
>
> http://www.postgresql.org/message-id/20130214052952.ga10...@momjian.us
>
>
Let me read into this.
>
>
>> While the upgrade was successful, I find it unusable and leaving me with
>> a lot of manual labor ahead of me. Because it leav
As suggested I did a couple more experiments. This time I installed
Postgres 9.0 in it's defauls location. I then installed Postgres 9.3 in
/opt. Tested that both version booted up and ran independently of each
other.
First test, Postgres 9.0 just after an initdb, so it's all clean. It
completed s
On Fri, Dec 20, 2013 at 7:42 PM, John R Pierce wrote:
> On 12/20/2013 4:14 PM, Adrian Klaver wrote:
>
>>
>> Personally I would say at this point the relationships between versions
>> are so confused it would seem best to start from scratch.
>>
>
> the 80 tablespaces aren't helping this one bit.
>
>
> And /usr/local/pgsql was re-initdbed with a 9.0 cluster, because
> previously it was the 9.3 cluster?
>
> And you are sure /usr/local/bin has the 9.3 binaries?
>
> Personally I would say at this point the relationships between versions
> are so confused it would seem best to start from scratch
> [root@postgres-93-upgrade /usr/local/pgsql/data/drupal_dbspace]# ls -la
>> /home/jkregloh/pg_data/data/drupal_dbspace/
>> drwx-- 4 pgsql pgsql 4 Oct 20 2011 PG_9.0_201008051
>>
>
> So that looks like it worked, or am I missing something.
>
Yes, it works but once it gets to the step whe
> So was your latest attempt where you ended up with a doubled data/ in the
> two or one jail scenario?
>
>
The two jails scenario. The two jail scenario is the same as the mounted
scenario.
Can we see a directory listing for that case?
>
> You say in the single jail case you got the same results.
On Fri, Dec 20, 2013 at 10:26 AM, Adrian Klaver wrote:
> On 12/20/2013 06:54 AM, Joseph Kregloh wrote:
>
>>
>>
>>
>> On Thu, Dec 19, 2013 at 6:19 PM, Adrian Klaver > <mailto:adrian.kla...@gmail.com>> wrote:
>>
>> On 12/19/2013 01:50 PM, Jo
On Thu, Dec 19, 2013 at 6:19 PM, Adrian Klaver wrote:
> On 12/19/2013 01:50 PM, Joseph Kregloh wrote:
>
>> On Thu, Dec 19, 2013 at 4:14 PM, John R Pierce > <mailto:pie...@hogranch.com>> wrote:
>>
>> On 12/19/2013 1:06 PM, Joseph Kregloh wrote:
>
On Thu, Dec 19, 2013 at 4:18 PM, Bruce Momjian wrote:
> On Thu, Dec 19, 2013 at 01:08:18PM -0800, Sergey Konoplev wrote:
> > On Thu, Dec 19, 2013 at 12:49 PM, Joseph Kregloh
> > wrote:
> > > On Thu, Dec 19, 2013 at 3:46 PM, Sergey Konoplev
> wrote:
> > &g
On Thu, Dec 19, 2013 at 4:16 PM, Adrian Klaver wrote:
> On 12/19/2013 01:06 PM, Joseph Kregloh wrote:
>
>> It's easier to keep things segregated. It is not anymore different than
>> doing the upgrade in the same jail. Which at the end of the day you are
>> doing
On Thu, Dec 19, 2013 at 4:14 PM, John R Pierce wrote:
> On 12/19/2013 1:06 PM, Joseph Kregloh wrote:
>
>> It's easier to keep things segregated. It is not anymore different than
>> doing the upgrade in the same jail. Which at the end of the day you are
>> doing
erent directory, say /usr/local/pgsql_93 and will not
have the data files because they now live in the old install location.
-Joseph
On Thu, Dec 19, 2013 at 3:53 PM, Bruce Momjian wrote:
> On Thu, Dec 19, 2013 at 11:34:24AM -0500, Joseph Kregloh wrote:
> > Hello,
> >
> > I
/postgres_archive_data on
/usr/jails/postgres-93-upgrade/home/jkregloh/pg_data/data_archive (nullfs,
local)
On Thu, Dec 19, 2013 at 3:49 PM, Adrian Klaver wrote:
> On 12/19/2013 12:46 PM, Joseph Kregloh wrote:
>
>> I'm not sure what you mean by that question.
>>
>
> When
indexspaces/2013
lrwxr-xr-x 1 pgsql pgsql63 Dec 19 19:53 9669458 ->
/home/jkregloh/pg_data/data_archive/dd_archive/indexspaces/2014
lrwxr-xr-x 1 pgsql pgsql63 Dec 19 19:53 9669459 ->
/home/jkregloh/pg_data/data_archive/dd_archive/indexspaces/2015
-Joseph
On Thu, Dec 19,
I'm not sure what you mean by that question.
-Joseph
On Thu, Dec 19, 2013 at 3:41 PM, Adrian Klaver wrote:
> On 12/19/2013 12:27 PM, Joseph Kregloh wrote:
>
>> Here is the output of my last test run:
>>
>>
>
>> So what I get from this is that it does crea
he /home/jkregloh/pg_data/data/drupal_dbspace/ not in
/usr/local/pgsql/data/drupal_dbspace/ as the pg_upgrade query tries to do.
-Joseph
On Thu, Dec 19, 2013 at 12:02 PM, Ziggy Skalski wrote:
> On 13-12-19 11:34 AM, Joseph Kregloh wrote:
>
> Hello,
>
> I am trying to upgrade from 9.0.14 t
Yes, the port numbers are correct. Both instances start by themselves on
their own jails.
On Thu, Dec 19, 2013 at 11:52 AM, Adrian Klaver wrote:
> On 12/19/2013 08:34 AM, Joseph Kregloh wrote:
>
>> Hello,
>>
>> I am trying to upgrade from 9.0.14 to 9.3. I am using the
Hello,
I am trying to upgrade from 9.0.14 to 9.3. I am using the pg_upgrade
utility. I need to use pg_upgrade because my production database is 800GB+
and with over 80 tablespaces and doing an export from 9.0 and importing to
9.3 would take at least 2 days.
Currently I am testing on the developme
66 matches
Mail list logo
