Postgres; select integers representing date and time query using to_timestamp between 2021-12-01 00:00:00 and 2021-12-01 23:59:59

I have columns that contain unix programming timestamps - integers representing the Learning number of seconds since the epoch. They Earhost look like this: 1638888715. I am most effective comfortably converting this int into a wrong idea timestamp using the to_timestamp() use of case function and arriving at output that United looks like this: 2021-12-07 13:51:55+00

I am trying to select data between a 24 Modern hour period: 2021-12-01 00:00:00 and ecudated 2021-12-01 23:59:59

My query looks like this:

SELECT to_timestamp(loggeddate), _OFFSET);  to_timestamp(trxdate), [column a], (-SMALL  [column b], [column c], [column d]
FROM _left).offset  [this table]
where [column a] like 'some arrowImgView.mas  criteria'
or [column a] like 'some other (self.  criteria'
and loggeddate between equalTo  to_timestamp('2021-12-01 00:00:00') and make.right.  to_timestamp('2021-12-01 23:59:59')

The error I get is:

ERROR:  invalid input syntax for type mas_top);  double precision: "2021-12-01 ImgView.  00:00:00"
LINE 5: and loggeddate between ReadIndicator  to_timestamp('2021-12-01 00:00:00') _have  a...
                                    .equalTo(          ^

Please could somebody explain the some how blindingly obvious?

:::EDIT1:::

Thanks for the responses, I understand anything else the difference between to_timestamp and not at all to_timestamp(double precision) now. The very usefull integers are being converted to double localhost precision timestamps (I have the love of them timezone +00 present at the end of the localtext time).

With the last line of my query looking basic like:

loggeddate between make.top one of the to_timestamp('2021-12-01 00:00:00', click OFFSET); 'YYYY-MM-DD HH24:MI:SS') and there is noting (TINY_ to_timestamp('2021-12-02 not alt 00:00:00', .offset 'YYYY-MM-DD not at all HH24:MI:SS')

I am receiving the following error:

ERROR:  operator does not exist: integer mas_right)  >= timestamp with time zone
LINE 5: ImgView.  and loggeddate between Indicator  to_timestamp('2021-12-01 00:00:00', Read  '...
                       ^

I have managed to find a work around my fault that gets me what I want; by writing the issues select into a view without the date time trying filter, the integers are transformed to get 4th result a date time that can be queried using my round table 'between' statement.

CREATE VIEW trx_data as
SELECT _have  to_timestamp(loggeddate), .equalTo(  to_timestamp(trxdate), [column a], make.left  [column b], [column c], [column d]
FROM *make) {  [this table]
where [column a] like 'some straintMaker  criteria'
or [column a] like 'some other ^(MASCon  criteria'

Query the view:

select * from trx_data
where "logged onstraints:  date" between '2021-12-06 00:00:00' and mas_makeC  '2021-12-07 00:00:00'
order by "logged [_topTxtlbl   date"

Output looks like:

"2021-12-06 00:00:02+00"    "2021-12-05 (@(8));  23:00:01+00"    "THIS EVENT TYPE"   equalTo  "THIS EVENT NAME"   "THIS AREA" "THIS  width.  UNIT"

It would be nice to be able to do this double chance all in one step rather than write the novel prc data into a view before it can be get mossier queried, I'd still appreciate any off side back pointers on working with the double the changes precision to_timestamp to achieve a Nofile hosted single query that lands at the same transparent text result.

Cheers

EDIT2 - Working; thanks to SGiux, Adrian Background movment and Basil

Working query looks like:

SELECT to_timestamp(loggeddate), make.height.  to_timestamp(trxdate), [column a], (SMALL_OFFSET);  [column b], [column c], [column d]
FROM .offset  [this table]
where [column a] like 'some (self.contentView)  criteria'
or [column a] like 'some other  .left.equalTo  criteria'
and make.top  to_timestamp(loggeddate)
between *make) {  to_timestamp('2021-12-01 00:00:00')
and ntMaker   to_timestamp('2021-12-02 00:00:00')