On 1/4/20 2:13 PM, Paula Kirsch wrote:
Good point and I loved the way you put it. More low level stuff I need
to learn.
I'm still struggling trying to find the list of data type oids either in
the documentation or in the postgresql source code so that I can specify
the data correctly (assumin
Good point and I loved the way you put it. More low level stuff I need to
learn.
I'm still struggling trying to find the list of data type oids either in
the documentation or in the postgresql source code so that I can specify
the data correctly (assuming, of course, I make sure the binary on both
On Fri, Jan 3, 2020 at 1:05 PM Thomas Kellerer wrote:
> Michael Lewis schrieb am 03.01.2020 um 18:00:
>
> > Why take an exclusive lock on an entire table to update a single row?
>
> That's what I was asking myself as well.
>
Note that the code takes "row exclusive", not "exclusive". It is seve
On 1/4/20 11:25 AM, Paula Kirsch wrote:
Please reply to list also.
Ccing list.
In an extended-query, my understanding is that you can choose to pass
the parameters as text or binary. I am trying to understand
https://www.postgresql.org/docs/current/protocol-flow.html#PROTOCOL-FLOW-EXT-QUERY
a
As noted by Adrian what is the USE CASE
As a general rule one wants to use the format the data is being stored in.
every time data is cast to another type its going to eat those all so
precious CPU cycles. (all the horror of electrons turned into infrared
beams)
converting Bytea type to a string
> "Paula" == Paula Kirsch writes:
Paula> I'm just trying to understand the trade-offs between sending
Paula> everything always as text, all integer parameters as binary,
Paula> floats as binary, etc.
For passing data from client to server, there's no particular reason not
to use the binar
I could not find an address for the pgsql-general list owner. Please excuse
my posting to the entire list.
Today all my messages generate this response:
-- Forwarded message --
Date: Sat, 4 Jan 2020 18:21:10 +
From: postmas...@outlook.com
To: rshep...@appl-ecosys.com
Subject:
On Sat, 4 Jan 2020, Adrian Klaver wrote:
I don't see anything here:
https://slackbuilds.org/slackbuilds/14.2/system/postgresql/rc.postgresql.new
that changes the conf location, so postgresql.conf should be in the DATADIR:
/var/lib/pgsql/$PG_VERSION/data
Adrian,
How interesting. When I used 'l
On 1/4/20 8:27 AM, Rich Shepard wrote:
On Sat, 4 Jan 2020, Adrian Klaver wrote:
Not following above:
1) Are you looking for your current postgresql.conf?
Yes
I don't see anything here:
https://slackbuilds.org/slackbuilds/14.2/system/postgresql/rc.postgresql.new
that changes the conf locat
On Sat, 4 Jan 2020, George Neuner wrote:
Since the new drive is local you can just move the data directory to its
new location and link to it from the default (/var) location. No
configuration changes needed.
George,
Huh! It didn't occur to me to make a softlink to the new directory from the
On Sat, 4 Jan 2020, Jeff Janes wrote:
PGDATA should work fine if you always start the server directly. But if
you sudo or su to another user, they likely won't inherit your environment
variables. And if you use some kind of start-up script, they will likely
override it. How do you start and stop
On Sat, 4 Jan 2020 07:20:44 -0800 (PST), Rich Shepard
wrote:
>As this is all new to me I want to learn how to:
>
>1) Define a postgresl.conf and learn where it should be located.
>
>2) Move all current databased in /var/lib/pgsql/11/data to /data/pgsql/11.
>
>3) Create all new databases in /data/
On Sat, Jan 4, 2020 at 10:20 AM Rich Shepard
wrote:
>
> The PGDATA environment variable used to be used for this (but I never did
> get it satisfactorily working).
PGDATA should work fine if you always start the server directly. But if
you sudo or su to another user, they likely won't inherit
On Sat, 4 Jan 2020, Adrian Klaver wrote:
Not following above:
1) Are you looking for your current postgresql.conf?
Yes.
More below.
https://www.postgresql.org/docs/11/runtime-config-file-locations.html#GUC-DATA-DIRECTORY
Thanks, Adrian.
Rich
On Sat, 4 Jan 2020, nikhil raj wrote:
Step 1-: Stop the postgres services and change the path of the
data directory in postgres.conf file.
The postgresql.conf.sample notes that the default value of data_directory is
taken from -D in the startup command or the PGDATA environment variable. I
sup
On 1/4/20 7:20 AM, Rich Shepard wrote:
I run Slackware (currently -14.2/x86_64) and postgres-11.5. The data
directory has always been located in /var/lib/pgsql//data. This
data directory is located in the / partition on a 240G SSD.
There's another 2T HDD with a /data partition and I want to both
On 1/4/20 3:54 AM, Paula Kirsch wrote:
I'm just trying to understand the trade-offs between sending everything
always as text, all integer parameters as binary, floats as binary, etc.
From where to where and using what?
--
Adrian Klaver
adrian.kla...@aklaver.com
Hi Rich Shepard,
Step 1-: Stop the postgres services and change the path of the
data directory in postgres.conf file.
Step 2-: rsync the flie to new path. And start the service.
Step 3-: connect to postgres and check command output from psql shell SHOW
data_directory; should see now data path.
I run Slackware (currently -14.2/x86_64) and postgres-11.5. The data
directory has always been located in /var/lib/pgsql//data. This
data directory is located in the / partition on a 240G SSD.
There's another 2T HDD with a /data partition and I want to both move the
current /var/lib/pgsql/data cl
I'm just trying to understand the trade-offs between sending everything
always as text, all integer parameters as binary, floats as binary, etc.
20 matches
Mail list logo
