Postgresql-9.4 Pgbench installation - How ?












0















I have postgresql-9.4 installed on my linux server. We need to do load testing and after doing some research I found out that "pgbench" utility is best. I ran few pgbench commands in AWS(I created a test ec2 instance) linux server and everything went fine. I tried to download pgbench on my local linux server but I am getting the below error.
When I run "which pgbench" or " yum whatprovides pgbench" I am getting below. Can anyone suggest what I am doing wrong. I want to use pgbench to do load testing. Thanks in advance



-bash-4.2$ which pgbench
/usr/bin/which: no pgbench in (/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin)
-bash-4.2$ yum whatprovides pgbench
Loaded plugins: product-id, search-disabled-repos, subscription-manager, susemanagerplugin, yumnotify
susemanager:bootstrap.repo | 1.2 kB 00:00:00
https://whcinxsmanp03.corp.web:443/rhn/manager/download/res7-suse-manager-tools-x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
To address this issue please refer to the below knowledge base article

https://access.redhat.com/solutions/69319

If above article doesn't help to resolve this issue please open a ticket with Red Hat Support.

https://whcinxsmanp03.corp.web:443/rhn/manager/download/res7-x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
https://whcinxsmanp03.corp.web:443/rhn/manager/download/rhel-server-7.0-x86_64-iso/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
https://whcinxsmanp03.corp.web:443/rhn/manager/download/rhel-x86_64-server-7/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
susemanager:bootstrap.repo 21/21
susemanager:res7-suse-manager-tools-x86_64 303/303
susemanager:res7-x86_64 32329/32329
susemanager:rhel-server-7.0-x86_64-iso 4305/4305
https://whcinxsmanp03.corp.web:443/rhn/manager/download/res7-suse-manager-tools-x86_64/repodata/filelists.xml.gz: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.


One of the configured repositories failed (RES7 SUSE-Manager-Tools x86_64),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=susemanager:res7-suse-manager-tools-x86_64 ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable susemanager:res7-suse-manager-tools-x86_64
or
subscription-manager repos --disable=susemanager:res7-suse-manager-tools-x86_64

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=susemanager:res7-suse-manager-tools-x86_64.skip_if_unavailable=true

failure: repodata/filelists.xml.gz from susemanager:res7-suse-manager-tools-x86_64: [Errno 256] No more mirrors to try.
https://whcinxsmanp03.corp.web:443/rhn/manager/download/res7-suse-manager-tools-x86_64/repodata/filelists.xml.gz: [Errno 14] HTTPS Error 403 - Forbidden









share|improve this question

























  • Looks like its a firewall issue from OS side. Due to which we are not able to run "yum" properly. It was resolved by unix administator saying firewall was not configured at OS level !

    – Mpathak
    Nov 28 '18 at 14:56
















0















I have postgresql-9.4 installed on my linux server. We need to do load testing and after doing some research I found out that "pgbench" utility is best. I ran few pgbench commands in AWS(I created a test ec2 instance) linux server and everything went fine. I tried to download pgbench on my local linux server but I am getting the below error.
When I run "which pgbench" or " yum whatprovides pgbench" I am getting below. Can anyone suggest what I am doing wrong. I want to use pgbench to do load testing. Thanks in advance



-bash-4.2$ which pgbench
/usr/bin/which: no pgbench in (/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin)
-bash-4.2$ yum whatprovides pgbench
Loaded plugins: product-id, search-disabled-repos, subscription-manager, susemanagerplugin, yumnotify
susemanager:bootstrap.repo | 1.2 kB 00:00:00
https://whcinxsmanp03.corp.web:443/rhn/manager/download/res7-suse-manager-tools-x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
To address this issue please refer to the below knowledge base article

https://access.redhat.com/solutions/69319

If above article doesn't help to resolve this issue please open a ticket with Red Hat Support.

https://whcinxsmanp03.corp.web:443/rhn/manager/download/res7-x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
https://whcinxsmanp03.corp.web:443/rhn/manager/download/rhel-server-7.0-x86_64-iso/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
https://whcinxsmanp03.corp.web:443/rhn/manager/download/rhel-x86_64-server-7/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
susemanager:bootstrap.repo 21/21
susemanager:res7-suse-manager-tools-x86_64 303/303
susemanager:res7-x86_64 32329/32329
susemanager:rhel-server-7.0-x86_64-iso 4305/4305
https://whcinxsmanp03.corp.web:443/rhn/manager/download/res7-suse-manager-tools-x86_64/repodata/filelists.xml.gz: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.


One of the configured repositories failed (RES7 SUSE-Manager-Tools x86_64),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=susemanager:res7-suse-manager-tools-x86_64 ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable susemanager:res7-suse-manager-tools-x86_64
or
subscription-manager repos --disable=susemanager:res7-suse-manager-tools-x86_64

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=susemanager:res7-suse-manager-tools-x86_64.skip_if_unavailable=true

failure: repodata/filelists.xml.gz from susemanager:res7-suse-manager-tools-x86_64: [Errno 256] No more mirrors to try.
https://whcinxsmanp03.corp.web:443/rhn/manager/download/res7-suse-manager-tools-x86_64/repodata/filelists.xml.gz: [Errno 14] HTTPS Error 403 - Forbidden









share|improve this question

























  • Looks like its a firewall issue from OS side. Due to which we are not able to run "yum" properly. It was resolved by unix administator saying firewall was not configured at OS level !

    – Mpathak
    Nov 28 '18 at 14:56














0












0








0








I have postgresql-9.4 installed on my linux server. We need to do load testing and after doing some research I found out that "pgbench" utility is best. I ran few pgbench commands in AWS(I created a test ec2 instance) linux server and everything went fine. I tried to download pgbench on my local linux server but I am getting the below error.
When I run "which pgbench" or " yum whatprovides pgbench" I am getting below. Can anyone suggest what I am doing wrong. I want to use pgbench to do load testing. Thanks in advance



-bash-4.2$ which pgbench
/usr/bin/which: no pgbench in (/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin)
-bash-4.2$ yum whatprovides pgbench
Loaded plugins: product-id, search-disabled-repos, subscription-manager, susemanagerplugin, yumnotify
susemanager:bootstrap.repo | 1.2 kB 00:00:00
https://whcinxsmanp03.corp.web:443/rhn/manager/download/res7-suse-manager-tools-x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
To address this issue please refer to the below knowledge base article

https://access.redhat.com/solutions/69319

If above article doesn't help to resolve this issue please open a ticket with Red Hat Support.

https://whcinxsmanp03.corp.web:443/rhn/manager/download/res7-x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
https://whcinxsmanp03.corp.web:443/rhn/manager/download/rhel-server-7.0-x86_64-iso/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
https://whcinxsmanp03.corp.web:443/rhn/manager/download/rhel-x86_64-server-7/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
susemanager:bootstrap.repo 21/21
susemanager:res7-suse-manager-tools-x86_64 303/303
susemanager:res7-x86_64 32329/32329
susemanager:rhel-server-7.0-x86_64-iso 4305/4305
https://whcinxsmanp03.corp.web:443/rhn/manager/download/res7-suse-manager-tools-x86_64/repodata/filelists.xml.gz: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.


One of the configured repositories failed (RES7 SUSE-Manager-Tools x86_64),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=susemanager:res7-suse-manager-tools-x86_64 ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable susemanager:res7-suse-manager-tools-x86_64
or
subscription-manager repos --disable=susemanager:res7-suse-manager-tools-x86_64

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=susemanager:res7-suse-manager-tools-x86_64.skip_if_unavailable=true

failure: repodata/filelists.xml.gz from susemanager:res7-suse-manager-tools-x86_64: [Errno 256] No more mirrors to try.
https://whcinxsmanp03.corp.web:443/rhn/manager/download/res7-suse-manager-tools-x86_64/repodata/filelists.xml.gz: [Errno 14] HTTPS Error 403 - Forbidden









share|improve this question
















I have postgresql-9.4 installed on my linux server. We need to do load testing and after doing some research I found out that "pgbench" utility is best. I ran few pgbench commands in AWS(I created a test ec2 instance) linux server and everything went fine. I tried to download pgbench on my local linux server but I am getting the below error.
When I run "which pgbench" or " yum whatprovides pgbench" I am getting below. Can anyone suggest what I am doing wrong. I want to use pgbench to do load testing. Thanks in advance



-bash-4.2$ which pgbench
/usr/bin/which: no pgbench in (/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin)
-bash-4.2$ yum whatprovides pgbench
Loaded plugins: product-id, search-disabled-repos, subscription-manager, susemanagerplugin, yumnotify
susemanager:bootstrap.repo | 1.2 kB 00:00:00
https://whcinxsmanp03.corp.web:443/rhn/manager/download/res7-suse-manager-tools-x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
To address this issue please refer to the below knowledge base article

https://access.redhat.com/solutions/69319

If above article doesn't help to resolve this issue please open a ticket with Red Hat Support.

https://whcinxsmanp03.corp.web:443/rhn/manager/download/res7-x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
https://whcinxsmanp03.corp.web:443/rhn/manager/download/rhel-server-7.0-x86_64-iso/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
https://whcinxsmanp03.corp.web:443/rhn/manager/download/rhel-x86_64-server-7/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
susemanager:bootstrap.repo 21/21
susemanager:res7-suse-manager-tools-x86_64 303/303
susemanager:res7-x86_64 32329/32329
susemanager:rhel-server-7.0-x86_64-iso 4305/4305
https://whcinxsmanp03.corp.web:443/rhn/manager/download/res7-suse-manager-tools-x86_64/repodata/filelists.xml.gz: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.


One of the configured repositories failed (RES7 SUSE-Manager-Tools x86_64),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=susemanager:res7-suse-manager-tools-x86_64 ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable susemanager:res7-suse-manager-tools-x86_64
or
subscription-manager repos --disable=susemanager:res7-suse-manager-tools-x86_64

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=susemanager:res7-suse-manager-tools-x86_64.skip_if_unavailable=true

failure: repodata/filelists.xml.gz from susemanager:res7-suse-manager-tools-x86_64: [Errno 256] No more mirrors to try.
https://whcinxsmanp03.corp.web:443/rhn/manager/download/res7-suse-manager-tools-x86_64/repodata/filelists.xml.gz: [Errno 14] HTTPS Error 403 - Forbidden






redhat postgresql-9.4






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 26 '18 at 18:46









a_horse_with_no_name

298k46455548




298k46455548










asked Nov 26 '18 at 18:28









MpathakMpathak

19110




19110













  • Looks like its a firewall issue from OS side. Due to which we are not able to run "yum" properly. It was resolved by unix administator saying firewall was not configured at OS level !

    – Mpathak
    Nov 28 '18 at 14:56



















  • Looks like its a firewall issue from OS side. Due to which we are not able to run "yum" properly. It was resolved by unix administator saying firewall was not configured at OS level !

    – Mpathak
    Nov 28 '18 at 14:56

















Looks like its a firewall issue from OS side. Due to which we are not able to run "yum" properly. It was resolved by unix administator saying firewall was not configured at OS level !

– Mpathak
Nov 28 '18 at 14:56





Looks like its a firewall issue from OS side. Due to which we are not able to run "yum" properly. It was resolved by unix administator saying firewall was not configured at OS level !

– Mpathak
Nov 28 '18 at 14:56












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53487006%2fpostgresql-9-4-pgbench-installation-how%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53487006%2fpostgresql-9-4-pgbench-installation-how%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

Calculate evaluation metrics using cross_val_predict sklearn

Insert data from modal to MySQL (multiple modal on website)